Unicast and broadcast protocol for wireless local area network ranging and direction finding

ABSTRACT

Disclosed embodiments facilitate wireless channel calibration, including ranging and direction finding, between wirelessly networked devices. In some embodiments. a method on a first station (STA) may comprise: transmitting a first NDPA frame to one or more second stations (STAs), the first NDPA frame comprising a first bit indicating that one or more subsequent frames comprise ranging or angular information; and transmitting, after a Short Interval Frame Space (SIFS) time interval, a second frame. The second frame may be one of: a Null Data Packet az (NDP_az) frame with information about a time of transmission of the NDP_az frame, or a Null Data Packet (NDP) frame, or a Beam Refinement Protocol (BRP) frame. The first NDPA frame may be unicast, multicast, or broadcast.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalPatent Application No. 62/300,879 entitled “Unicast and BroadcastProtocol for Wireless Local Area Network Ranging and Direction Finding,”filed Feb. 28, 2016, which is assigned to the assignee hereof andincorporated by reference in its entirety herein.

FIELD

The subject matter disclosed herein relates to wireless communicationand specifically to unicast, multicast, and/or broadcast protocols forsounding, ranging and/or direction finding in wireless communicationsystems.

BACKGROUND

It is often desirable to perform positioning functions on user equipment(UE) such as a mobile terminal, a cellular phone or other mobile device.The terms “location” and “position” are synonymous and are usedinterchangeably herein. For example, in wireless systems based on theIEEE 802.11 standard, positioning may be performed using Round Trip Time(RTT) measurements between an Access Point (AP) and User Equipment (UE),which may take the form of a mobile station, cell phone, wearable,handheld computing device, or some other user device.

In modern wireless systems, multiple antennas at the transmitter andreceiver may be used to implement multiple input/multiple output (MIMO).MIMO facilitates parallel delivery of multiple spatially multiplexeddata signals, which are referred to as multiple spatial streams. Inaddition, “beamforming” may be used for directional signal transmissionor reception. In beamforming, elements in a phased array antenna arecombined so that signals at some angles experience constructiveinterference, while others experience destructive interference, so thatthe beam may be “steered” in a desired direction. Beamforming can beused to achieve spatial selectivity at the transmitting and receivingends. Techniques to facilitate beamforming calibration may thereforeprovide improved UE location determination and/or channelcharacterization.

SUMMARY

Disclosed embodiments facilitate information exchange between wirelessSTAs in part, by leveraging existing NDPA/NDP exchanges to send angularinformation for RTT determination purposes. Disclosed embodiments alsofacilitate information exchange between wireless STAs based, in part, onthe use of CBF frames to transmit CFI. The CBF, NDP and/or NDPA framesabove, may be used, in some embodiments, in a broadcast or multicastfashion. In some embodiments, BRP frames (e.g. used in 60 GHz) may beused with an NDPA/NDP framework to form a unified protocol Disclosedembodiments also facilitate symmetric RTT/AoA/AoD/Azimuth exchange

In some embodiments, a method on a first station (STA) may comprise:transmitting a first NDPA frame to one or more second stations (STAs),the first NDPA frame comprising a first bit indicating that one or moresubsequent frames comprise ranging or angular information; andtransmitting, after a Short Interval Frame Space (SIFS) time interval, asecond frame, wherein the second frame may be one of: a Null Data Packetaz (NDP_az) frame with information about a time of transmission of theNDP_az frame, or a Null Data Packet (NDP) frame, or a Beam RefinementProtocol (BRP) frame

In a further aspect, a first station (STA) may comprise: a memory, and aprocessor coupled to the memory, wherein the processor is configured to:transmit, at a first time, a first NDPA frame to one or more secondstations (STAs), the first NDPA frame comprising a first bit indicatingthat one or more subsequent frames comprise ranging or angularinformation; and transmit, after a Short Interval Frame Space (SIFS)time interval from the first time, a second frame, wherein the secondframe is one of: a Null Data Packet az (NDP_az) frame with informationabout a time of transmission of the NDP_az frame, or a Null Data Packet(NDP) frame, or a Beam Refinement Protocol (BRP) frame.

Disclosed embodiments also pertain to a first station (STA) comprising:means for transmitting a first NDPA frame to one or more second stations(STAs), the first NDPA frame comprising a first bit indicating that oneor more subsequent frames comprise ranging or angular information; andmeans for transmitting, after a Short Interval Frame Space (SIFS) timeinterval, a second frame, wherein the second frame is one of: a NullData Packet az (NDP_az) frame with information about a time oftransmission of the NDP_az frame, or a Null Data Packet (NDP) frame, ora Beam Refinement Protocol (BRP) frame.

In another aspect a non-transitory computer-readable medium may compriseprogram code executable by a processor to: transmit a first NDPA frameto one or more second stations (STAs), the first NDPA frame comprising afirst bit indicating that one or more subsequent frames comprise rangingor angular information; and transmit, after a Short Interval Frame Space(SIFS) time interval, a second frame, wherein the second frame is oneof: a Null Data Packet az (NDP_az) frame with information about a timeof transmission of the NDP_az frame, or a Null Data Packet (NDP) frame,or a Beam Refinement Protocol (BRP) frame.

The methods disclosed may be performed by one or more of APs, non-APSTAs, UEs, etc. using various protocols. Embodiments disclosed alsorelate to software, firmware, and program instructions created, stored,accessed, read or modified by processors using non-transitory computerreadable media or computer readable memory.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will be described, by way of example only,with reference to the drawings.

FIG. 1 shows a schematic block diagram illustrating certain exemplaryfeatures of a non-AP STA shown as UE 100 enabled to perform wirelesscommunication including unicast, multicast, and/or broadcast, andwireless medium characterization in a wireless environment in accordancewith certain embodiments presented herein.

FIG. 2 shows a simplified architecture of a wireless communicationsystem 200 in accordance with certain embodiments presented herein.

FIG. 3 shows schematic block diagram illustrating AP 240 enabled toperform wireless communication including unicast, multicast, and/orbroadcast, and wireless medium characterization in a wirelessenvironment in accordance with certain embodiments presented herein.

FIG. 4A shows an exemplary NDPA frame 400 with information pertaining toa subsequent NDP frame in accordance with certain embodiments presentedherein.

FIG. 4B shows the format of the Sounding Dialog Token field 430including a Reserved subfield 432 with a 2-bit length and SoundingDialog Token Number subfield 434 in accordance with certain embodimentspresented herein.

FIG. 5A shows an example unicast message flow 500 between an initiator510 (e.g. AP 240) and responder (e.g. UE 100) in accordance with certainembodiments presented herein.

FIG. 5B shows an example unicast message flow 550 between an initiator552 (e.g. AP 240) and a responder identified as Responder 1 554 (e.g.non-AP STA/UE 100), in accordance with certain embodiments presentedherein.

FIG. 5C shows the amount of CFI data that may be transmitted from oneSTA to another STA for different antenna configurations.

FIG. 5D shows the format of a VHT MIMO Control field, which may formpart of a Compressed Beamforming Feedback (CBF) frame.

FIG. 5E shows a unicast message flow 590 with NDPA 593 announcing asubsequent frame (NDP_az, NDP, or BRP) sent according to some disclosedembodiments.

FIG. 6 shows an example message flow 600 between FTM Initiator 605 (e.g.AP 240) and two FTM responders FTM Responder 1 610 and FTM Responder 2615 (e.g. UEs 100-1 and 100-2), where an NDPA is broadcast to both FTMResponder 1 and FTM Responder 2.

FIG. 7A shows an example message flow 700 between Initiator 705 (e.g. AP240) and two responders Responder 1 710 and Responder 2 715 (e.g. UEs ornon-AP STAs 100-1 and 100-2), where an NDPA is broadcast/multicast toresponders Responder 1 and Responder 2.

FIG. 7B shows a format for an example Beamforming Report Poll frame inaccordance with certain embodiments presented herein.

FIG. 8A shows an example Fine Timing Measurement (FTM) frame, which mayinclude AoA, AoD, and/or other information in accordance with certainembodiments presented herein.

FIGS. 8B and 8C show the formats of example AoA field 830 and AoD field840 in accordance with certain embodiments presented herein.

FIG. 8D shows an example Fine Timing Measurement (FTM) No Ack frame 800indicating a request for an FTM Acknowledgement (FTM Ack).

FIG. 8E is an example 3-dimensional coordinate system 880 forrepresenting the position of a STA using a radius “r” and angles “theta”and “phi.”

FIG. 9A shows an example symmetric unicast message flow between aninitiator (e.g. AP 240) and a responder (e.g. UE 100) with FTM framesinclude a CFI field in accordance with certain embodiments presentedherein.

FIG. 9B shows an example unicast message flow between an initiator (e.g.AP 240) and a responder (e.g. UE 100) where FTM frames include a CFIfield, an Angle of Arrival (AoA) field and/or an Angle of Departure(AoD) field and/or an Azimuth field and/or a Range field in accordancewith certain embodiments presented herein.

FIG. 9C shows an example symmetric message flow between an initiator(e.g. AP 240) and a responder (e.g. UE 100) where an NDPA announces abroadcast NDP and FTM frames include an Angle of Arrival (AoA) fieldand/or an Angle of Departure (AoD) field in accordance with certainembodiments presented herein.

FIG. 10 shows a multicast non-symmetric message flow 1000 with multipleinitiators where the FTM Responder does not share information.

FIG. 11 shows a multicast symmetric message flow 1100 with multipleinitiators where the FTM Responder shares information.

FIG. 12 shows a multicast symmetric message flow 1200 with multipleinitiators with the ranging bit set.

FIG. 13 shows a multicast symmetric message flow 1300 with multipleinitiators with the ranging bit not set.

FIG. 14A shows a multicast symmetric Orthogonal Frequency DivisionMultiple Access (OFDMA) or downlink Multi User MIMO message flow 1400with multiple initiators where information for all initiators isreceived within a SIFS interval.

FIG. 14B shows a multicast symmetric Orthogonal Frequency DivisionMultiple Access (OFDMA) or downlink Multi User MIMO message flow 1487with multiple initiators where information for all initiators isreceived within a SIFS interval.

FIG. 15 shows an example flowchart illustrating a method 1500 formessage flow between an initiator (e.g. a first STA) and responder (oneor more second STAs/UEs) in accordance with certain embodimentspresented herein.

DETAILED DESCRIPTION

Embodiments disclosed facilitate wireless communication between devices.In some embodiments, wireless communication is facilitated through theuse of protocols or modifications to protocols that assist in channelcalibration. In some embodiments, channel calibration may includeperforming measurements related to sounding, ranging, and/or directionfinding. In some embodiments, disclosed techniques may be used inwireless environments to facilitate ranging and direction findingbetween devices. In a set of wirelessly networked devices, disclosedembodiments may facilitate ranging and/or direction finding between twodevices (one-to-one) and/or multicast (from one-to-many) and/orbroadcast (one to all) devices. The term “unicast” is used to indicatetransmission of signals from a STA to a single device, whereas the term“multicast” is used to indicate transmission of signals from a STA to aplurality of devices. The term “broadcast” is used to refer totransmission of signals from a STA to all devices authorized to and/orcapable of receiving the transmitted signal.

In modern wireless systems, multiple antennas at the transmitter andreceiver may be used to implement multiple input/multiple output (MIMO).MIMO facilitates parallel delivery of multiple spatially multiplexeddata signals, which are referred to as multiple spatial streams.Further, in multi-user MIMO (MU-MIMO), an AP may simultaneously transmitto multiple client UEs and beamforming may be used for directionalsignal transmission or reception. In MU-MIMO, the term “downlink” refersto communication, which may occur in parallel, from an AP (transmittedby the AP) to one or more UEs, while the term “uplink” refers tocommunication, which may occur in parallel, to an AP (received by theAP) from one or more UEs.

In beamforming, elements in a phased array antenna are combined so thatsignals at some angles experience constructive interference, whileothers experience destructive interference. Beamforming can be used toachieve spatial selectivity at the transmitting and receiving ends. Forexample, in 802.11ac, an AP may use a Null Data Packet Announcement(NDPA), which may be immediately followed by a Null Data Packet (NDP) todetermine how to direct a transmission. The NDP can be a physical layer(PHY) frame without data but with a known format and may be used tocalibrate the channel. For example, the UE(s) (receivers) receiving theNDP may respond with a “beamforming matrix”, which provides someinformation about the channel. The information can be used by an AP(transmitter) to focus subsequent transmissions.

However, while the beamforming matrix can include some channel relatedinformation, the existing beamforming matrix does not includeinformation about Angle of Arrival (AoA), Angle of Departure (AoD),Azimuth, Channel Frequency Response (CFR), Channel Impulse Response(CIR), Power Delay Profile (PDP), First Arrival Correction (FAC), and/orother channel calibration metrics between communicating STAs. Further,the above information cannot be derived from the beamforming matrix.Therefore, additional ranging/sounding message exchanges are often usedto obtain the above information thereby increasing system overhead, andlatency, which may adversely affecting system performance metrics.

Some disclosed embodiments pertain to beamforming calibrationtechniques, which facilitate improved UE location determination and/orchannel characterization. Further, disclosed embodiments also facilitatethe use of multiple transmit chains. For example, some disclosedembodiments may exploit the Null Data Packet (NDP) frame structure tofacilitate utilization of multiple transmit chains. In addition,disclosed embodiments provide techniques for exchange of informationincluding one or more of: Angle of Arrival (AoA), Angle of Departure(AoD), Azimuth, Channel Frequency Response (CFR), Channel ImpulseResponse (CIR), Power Delay Profile (PDP), First Arrival Correction(FAC), and/or other channel calibration parameters/metrics between twocommunicating STAs, which are also referred to herein as “channelcalibration parameters”, “channel calibration metrics” or “channelcharacterization information”. In some embodiments, the above channelcalibration parameters/metrics may be determined and exchanged betweencommunicating STAs with fewer frame exchanges. For example, in someembodiments, one or more of: frame structure, and/or informationelements in frames, and/or message exchange protocols may be leveragedto determine and/or exchange calibration parameters/metrics. Exampleembodiments are described further herein. Disclosed techniques may alsobe used to facilitate location determination including determination ofmicro-locations. In some embodiments, the location determination may bebased on one or more of the above channel calibration parameters. Forexample, disclosed techniques may be embodied in an application on a UE,which may direct a user to a shelf containing a desired product in astore. As other examples, disclosed techniques may be used insurveillance cameras and/or drone navigation. The example message flows,frame formats, and/or information elements described herein may becompatible, in some respects with specifications, diagrams, andguidelines found in some 802.11 standards.

The term “Angle of Arrival” (AoA) refers to a direction of propagationof a radio-frequency wave incident on an antenna array relative toorientation of the antenna array. As one example, AoA may be determinedbased on the Time Difference of Arrival (TDOA) or phase differencemeasurements of a radio wave received at individual elements of anantenna array. Conversely, the term “Angle of Departure” (AoD) refers toa direction of propagation of a radio-frequency wave transmitted from anantenna array relative to orientation of the antenna array. In someembodiments, AoA and AoD may determined by a STA based on signalsexchanged with another STA. For example, a STA, such as a receiver, mayresolve AoA and AoD based on signals exchanged with another STA.

Any suitable technique may be used to estimate AoA information of framesreceived by a responder device and/or to estimate AoD information forframes transmitted from a responder device. For at least someembodiments, the responder device may use a number of different antennapatterns when estimating the AoA information of frames received from theinitiator device. More specifically, when the responder device includesa number N≥2 antennas, the responder device may selectively enabledifferent combinations of the antennas and estimate the channelconditions for a corresponding number of different antenna patterns.Angular information may be obtained using various techniques including,but not limited to: correlation; maximum likelihood estimation; MultipleSignal Classification (MUSIC) techniques, including variants such asRoot-MUSIC, Cyclic MUSIC, or Smooth MUSIC; Estimation of SignalParameters using Rotational Invariance Techniques (ESPRIT); MatrixPencil, etc.

The term CFR for an i^(th) transmitting (Tx) antenna and a j^(th)receiving (Rx) antenna is also denoted by H_(ij)(k) for a tone k. Theterm CIR denoted by h_(ij)[n] refers to the inverse Fast FourierTransform of the CFR, for the i^(th) Tx antenna and a j^(th) Rx antenna.In some embodiments, information exchanged between two communicatingSTAs may include a subset of information in the CIR (CIR′), which maycapture the first arrival information. The length of CIR′ may befunction of the accuracy of the estimation of first arrival information.The term Channel Feedback Information (CFI) is used herein to refer toCFR, or CIR, or CIR′ or PDP or FAC. For example, a CompressedBeamforming (CBF) frame or another frame may include a CFI field. TheCFI field may include one or more of Channel Frequency Response (CFR)information, or Channel Impulse Response (CIR) information, or a subsetof the CIR information with first arrival information, or Power DelayProfile (PDP) information, or First Arrival Correction (FAC)information. The PDP is a measure of signal intensity received through amultipath channel as a function of time delay. FAC time informationfacilitates greater accuracy in the timing of communications between twoSTAs, which may improve quality in positioning applications.

The term station or “STA” may refer to a device with a Medium AccessControl (MAC) identifier coupled to a wireless network. A STA may beviewed as a logical entity that is a singly addressable instance of amedium access control (MAC) and physical layer (PHY) interface to awireless medium. A STA may take the form of a non-AP STA, which refersto devices such as a mobile station, cellular phone, or a computingdevice such as a wearable device, laptop, handheld, tablet etc, oranother entity coupled to the wireless network. A STA may also take theform of an Access Point STA (AP STA), which refers to APs that providewireless connectivity to one or more non-AP STAs. An AP STA may be incommunication with one or more non-AP devices and/or with other AP STAs.In some instances, in the description below, a STA may also be referredto as an “initiator” or as a “responder” for ease of explanation todistinguish from a STA that initiates a sequence of events from a STAthat responds to the initiated sequence. A “STA” may function as both an“initiator” and a “responder”. STAs may be mobile or stationary.

A STA may also take the form of “user equipment” (UE) or “mobilestation” such as a cellular or other wireless communication device,personal communication system (PCS) device, personal navigation device(PND), Personal Information Manager (PIM), Personal Digital Assistant(PDA), laptop or other suitable mobile device which is capable ofreceiving wireless communication and/or navigation signals. The term UEis also intended to include devices which communicate with a personalnavigation device (PND), such as by short-range wireless, infrared,wireline connection, or other connection—regardless of whether satellitesignal reception, assistance data reception, and/or position-relatedprocessing occurs at the device or at the PND.

FIG. 1 shows a schematic block diagram illustrating certain exemplaryfeatures of a non-AP STA shown as UE 100 enabled to perform wirelesscommunication including unicast, broadcast, and wireless mediumcharacterization in a MU-MIMO environment in accordance with certainembodiments presented herein. In some embodiments, UE 100 may take theform of a wearable user device, such as a wristwatch, spectacles etc.,where one or more functional components of UE 100 may be physicallyseparate but operationally coupled to other functional components. Forexample, display 190 may be physically separate but operationallycoupled processor(s) 150 and/or other functional units in UE 100.

UE 100 may, for example, include one or more processing units orprocessor(s) 150 and memory 130. UE 100 may also include a wirelessnetwork interface 105. In some embodiments, wireless network interfacemay include transmitter 112 and receiver 114. In some embodiments, UE100 may further comprise computer-readable medium 160 and display 190.The components above may be operatively coupled to each other with oneor more connections 120 (e.g., buses, lines, fibers, links, etc.). Incertain example implementations, all or part of UE 100 may take the formof a chipset, and/or the like. Further, UE 100 may optionally include ascreen or display 190 capable of rendering images of various types.

In some embodiments, processor(s) 150 may also receive input fromtransceiver 110, which may receive wireless signals through one or moreantennas 105 which may be used for signal transmission and receptionusing MIMO/MU-MIMO. Transceiver 110 may, for example, include atransmitter 112 enabled to transmit one or more wireless signals overone or more types of wireless communication networks and a receiver 114to receive one or more signals transmitted over one or more types ofwireless communication networks. For example, transceiver 110 may becapable of communication with a Wireless Local Area Network (WLAN),which may be based on IEEE 802.11 standards, Wireless Personal AreaNetwork (WPAN), which may be based on IEEE 802.15 standards and/or aWide Area Network (WAN) based on one or more cellular communicationstandards.

Processor(s) 150 may be implemented using a combination of hardware,firmware, and software. In some embodiments, processor(s) 150 mayperform position determination and/or location assistance functionsbased on information derived from wireless measurements by UE 100 eitherindependently, and/or in conjunction with received data or measurementsfrom other STAs. In some embodiments, processor(s) 150, may includetransceiver 110, and/or other components as part of a single chip,integrated circuit, or package.

Processor(s) 150 may use some or all of the received signals and/orinformation to determine channel characterization information includingTime Difference of Arrival (TDOA), Round Trip Time (RTT), ReceivedSignal Strength Indication (RSSI), CFR, CIR, PDP, FAC, etc. At locationswhere wireless signals are available, position determination may beperformed based, in part, on the channel characterization informationand/or a variety of techniques described herein. For example, techniquesincluding RTT measurements, TDOA, Reference Signal Time Difference(RSTD), Advanced Forward Link Trilateralation (AFLT), hybrid techniques,Received Signal Strength Indicator (RSSI) based measurements, and/orsome combination of the above may be used for position determination.

As one example, processor(s) 150 may determine, record, and/or receive:timestamps associated with a time of reception/arrival (TOA) and/ortransmission/departure (TOD) of signals, which may be used to determineRTT and/or a distance between UE 100 and one or more other devices.Further, AoA, AoD, and other characteristics and parameters describedherein may be used to determine or estimate a location/micro-location ofdevices communicating with UE 100. In some embodiments, the measurementsand/or results obtained from measurements may be included in one or moreframes exchanged between two STAs, such as between UE 100 and anotherdevice in accordance with one or more protocols described herein.

The elements and methodologies described herein may be implemented byvarious means depending upon the application. For example, theseelements and methodologies may be implemented in hardware, firmware,software, or any combination thereof. For example, for a hardwareimplementation, the processor(s) 150 may be implemented within one ormore application specific integrated circuits (ASICs), digital signalprocessors (DSPs), digital signal processing devices (DSPDs),programmable logic devices (PLDs), field programmable gate arrays(FPGAs), processors, controllers, micro-controllers, microprocessors,electronic devices, other electronic units designed to perform thefunctions described herein, or a combination thereof.

For a firmware and/or software implementation, the methodologies may beimplemented using program code, microcode, procedures, functions, and soon that perform the functions described herein. Any machine-readablemedium tangibly embodying instructions may be used in implementing themethodologies described herein. For example, program code, which may bestored in a non-transitory computer-readable medium 160 and/or memory130, may be read and executed by processor(s) 150.

Memory may be implemented within processor(s) 150 or external toprocessor(s) 150. As used herein the term “memory” refers to any type oflong term, short term, volatile, nonvolatile, or other memory and is notto be limited to any particular type of memory or number of memories, ortype of media upon which memory is stored. Memory 130 may include, forexample, a primary memory and/or a secondary memory. Primary memory mayinclude, for example, a random access memory, read only memory, etc.While illustrated in this example as being separate from processor(s)150, it should be understood that all or part of a primary memory may beprovided within or otherwise co-located/coupled with processor(s) 150.If implemented in firmware and/or software, the functions may be storedas one or more instructions or program code on a computer-readablemedium, such as medium 160 and/or secondary memory. Examples includecomputer-readable media encoded with computer programs and dataassociated with or used by the program.

Computer-readable medium 160 includes physical computer storage media. Astorage medium may be any available medium that can be accessed by acomputer. By way of example, and not limitation, such non-transitorycomputer-readable media can comprise RAM, ROM, EEPROM, CD-ROM, flashmemory, or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code in the form of instructions and/or data and thatcan be accessed by a computer; disk and disc, as used herein, includescompact disc (CD), laser disc, optical disc, digital versatile disc(DVD), floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

For example, the computer-readable medium including program code storedthereon may include program code to support wireless communicationincluding unicast, broadcast, and wireless medium/channelcharacterization in a MU-MIMO environment in accordance with certainembodiments presented herein. The program code may further supportwireless channel characterization, including sounding, ranging and/orposition determination. For example, the code may support one or more ofAFLT/RTT/RSSI/RSTD/TDOA/AoA/AoD, and other location determinationtechniques and/or channel characterization.

In some embodiments, instructions and/or data may be provided over acommunication channel. For example, a communication apparatus mayinclude a transceiver 110, which may receive signals through receiver114 indicative of instructions and data. The instructions and data maycause one or more processors to implement wireless communication and/orwireless channel characterization (e.g. in a MU-MIMO environment),including ranging and/or position determination. The instructions anddata may also cause one or more processors to implement functionsoutlined herein.

FIG. 2 shows a simplified architecture of a wireless communicationsystem 200 in accordance with certain embodiments presented herein.System 200 may include non-AP STAs such as UEs 100-1 through 100-n(collectively referred to as UEs 100), and AP STAs such as APs 240-1through 240-4 (collectively referred to as STAs 240), which maycommunicate over WLAN 230. In some embodiments, UEs 100 and APs 240 maycommunicate with server 250 over WLAN 230. While system 200 illustratesa few UEs 100 and APs 240, the number of UEs 100 and APs 240 may bevaried in accordance with various design parameters and may include asmaller or larger number of UEs 100 and/or APs 240. In some embodiments,one or more UEs 100 and/or APs 240 may comprise multiple antennas andmay support MIMO, including MU-MIMO.

In some embodiments, UEs 100 and APs 240 may communicate over a WLANnetwork, which may be based on IEEE 802.11 or compatible standards. Insome embodiments, UEs 100 and APs 240 may communicate using variants ofthe IEEE 802.11 standards. For example, UEs 100 and APs 240 maycommunicate using 802.11ac on the 5 GHz band, which may support MIMO,MU-MIMO and multiple spatial streams. In some embodiments, UEs 100 andAPs 240 may communicate using some of the above standards, which mayfurther support one or more of Very High Throughput (VHT) (as describedin the above standards) and High Efficiency WLAN (HEW), and/orbeamforming with standardized sounding and feedback mechanisms. In someembodiments, UEs 100 and/or APs 240 may additionally support legacystandards for communication with legacy devices.

In some embodiments, UEs 100 and/or APs 240 may be connected with one ormore additional networks, such as a cellular carrier network, asatellite positioning network, WPAN access points, and the like (notshown in FIG. 2). In some embodiments, UEs 100 and/or APs 240 may becoupled to a wireless wide area network (WWAN) (not shown in FIG. 2). AWWAN may be a Code Division Multiple Access (CDMA) network, a TimeDivision Multiple Access (TDMA) network, a Frequency Division MultipleAccess (FDMA) network, an Orthogonal Frequency Division Multiple Access(OFDMA) network, a Single-Carrier Frequency Division Multiple Access(SC-FDMA) network, Long Term Evolution (LTE), WiMax, and so on.

A CDMA network may implement one or more radio access technologies(RATs) such as cdma2000, Wideband-CDMA (W-CDMA), and so on. Cdma2000includes IS-95, IS-2000, and IS-856 standards. A TDMA network mayimplement Global System for Mobile Communications (GSM), DigitalAdvanced Mobile Phone System (D-AMPS), or some other RAT. GSM, W-CDMA,and LTE are described in documents from 3GPP. Cdma2000 is described indocuments from a consortium named “3rd Generation Partnership Project 2”(3GPP2). 3GPP and 3GPP2 documents are publicly available.

As illustrated in FIG. 2, UE 100 may also communicate with server 250-1through network 230 and APs 240, which may be associated with network230. UE 100 may receive and measure signals from APs 240, which may beused for position determination. In some embodiments, APs 240 may formpart of a wireless communication network 230, which may be a wirelesslocal area network (WLAN). For example, a WLAN may be an IEEE 802.11xnetwork.

Reference is now made to FIG. 3, which is a schematic block diagramillustrating AP 240. In some embodiments, AP 240 may be enabled toperform wireless communication (including unicast, multicast, andbroadcast) and wireless medium characterization. For example, thewireless communication and/or wireless medium characterization may beperformed in a MU-MIMO environment in accordance with certainembodiments presented herein. In some embodiments, UE 100 may serve asan AP 100.

In some embodiments, AP 240 may include, for example, one or moreprocessor(s) 350, memory 330, coupled storage 360, and transceiver 390,which may be operatively coupled with one or more connections 320 (e.g.,buses, lines, fibers, links, etc.). Transceiver 390 may be capable ofcommunication with a Wireless Local Area Network (WLAN), which may bebased on the IEEE 802.11 standard (or variants thereof), WirelessPersonal Area Network (WPAN), which may be based on IEEE 802.15 and/or aWide Area Network (WAN) based on one or more cellular communicationstandards. In some embodiments, transceiver 390 may be coupled to one ormore antennas 305, which may be used for signal transmission and/orreception using MIMO/MU-MIMO.

In some embodiments, AP 240 may also interface with wired networksthrough communications interface 380 to obtain a variety of networkconfiguration related information, such as service set identifiers(SSIDs), basic service set identification (BSSID), network identifiersand/or timing information. Processor(s) 350 may use some or all of thereceived information to generate CFI, TDOA, RTT, RSSI, CFR, CIR, PDP,Range, AOA, AOD, Azimuth, and other channel characterization informationin accordance with certain with disclosed embodiments.

Processor(s) 350 may be implemented using a combination of hardware,firmware, and software, or any combination thereof. For a hardwareimplementation, the processing unit 950 may be implemented within one ormore application specific integrated circuits (ASICs), digital signalprocessors (DSPs), digital signal processing devices (DSPDs),programmable logic devices (PLDs), field programmable gate arrays(FPGAs), processors, controllers, micro-controllers, microprocessors,electronic devices, other electronic units designed to perform thefunctions described herein, or a combination thereof. For a firmwareand/or software implementation, the methodologies may be implementedusing procedures, functions, and so on that perform the functionsdescribed herein.

Any machine-readable medium tangibly embodying instructions may be usedin implementing the methodologies described herein. For example,software may be stored in removable media drive 370, which may supportthe use of non-transitory computer-readable media 378, includingremovable media. Program code may be resident on non-transitory computerreadable media 378 and/or memory 330 and may be read and executed byprocessors 350. For example, the computer-readable medium includingprogram code stored thereon may include program code to support wirelesscommunication (including unicast, multicast, and broadcast), and/orwireless medium characterization (including in a MIMO/MU-MIMO)environment in accordance with certain embodiments presented herein.Memory 330 may be implemented within processors 350 or external to theprocessors 350.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to a non-transitorycomputer-readable medium 378. As such, in certain exampleimplementations, the methods and/or apparatuses presented herein maytake the form in whole or part of a removable media drive 370 that mayinclude non-transitory computer readable medium 378 with computerimplementable instructions stored thereon, which if executed by at leastone processing unit 350 may be operatively enabled to portions of theexample operations including message flows and protocols describedherein.

FIG. 4A shows an exemplary NDPA frame 400 with information pertaining toa subsequent NDP frame in accordance with certain embodiments presentedherein. In some embodiments, NDPA frame 400 may take the form of an802.11ac NDPA frame as defined in “Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications,” IEEEP802.11-REVmc™/D5.0, January 2016, Draft Standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks—Specific requirements, (hereinafter“WLAN MAC & PHY Specifications”) § 8.3.1.20, at 621-622, which isincorporated by reference in its entirety herein.

In some embodiments, NDPA frame may include Duration field 415, RA(Recipient Address) field 420, TA (Transmitter Address) field 425,Sounding Dialog token 430, STA Info field(s) 435-1 . . . 435-n, and FCSfield 440. The NDPA frame contains at least one STA Info field. Thesefields are further described in the WLAN MAC & PHY Specificationsdocument.

In some embodiments, when the NDP Announcement frame (e.g. VHT NDPAincludes more than one STA Info field 435, the RA field 420 of the NDPAnnouncement frame can be set to the broadcast address. When the VHT NDPAnnouncement frame includes a single STA Info field 435, the RA field420 of the VHT NDP Announcement frame can be set to the MAC address ofthe VHT beamformee. The TA field may, for example, be set to the addressof a UE 100 transmitting the VHT NDP Announcement frame.

The format of the Sounding Dialog Token field 430 is shown in FIG. 4Band includes Reserved subfield 432 with a 2-bit length and SoundingDialog token number subfield 434. The Sounding Dialog Token Numbersubfield in the Sounding Dialog Token field contains a value selected bythe AP (beamformer) to identify NDPA frame 400.

In some embodiments, a first bit in Reserved subfield 432 may be used bythe initiator to indicate to the responder that the immediatelysubsequent NDP is to be used for ranging. In some embodiments, a secondbit in the Reserved subfield 432 may be used to indicate symmetricranging, to indicate that one side (e.g. the initiator) is willing toshare information, such as ranging information (e.g. captured and/ordetermined by the initiator). In the example embodiments below, use ofNDP frames for ranging and symmetric/asymmetric ranging may be indicatedby appropriately configuring bits in Reserved subfield 432. In someembodiments, portions of other information elements in NDPA frame 400may be used to indicate: (i) that a subsequent NDP frame is to be usedfor ranging; and/or (ii) that the initiator is willing to share rangingand/or other measured/determined channel characterization information.

In some embodiments, NDP frames, which may be transmitted from multipleantennas, may be leveraged to determine AoA, AoD, and other parameters.In some embodiments, the AoA, AoD and other determined information maybe included in an FTM frame thereby facilitating location determination.In some embodiments, by determining AoA, AoD, and RTT, a device may beable to determine its 3D location based on an exchange of FTM frameswith one other device with a known location thereby decreasing networktraffic, lowering overhead, and/or facilitating quicker positiondetermination. In the description below, a STA requesting a specificranging/sounding or other operation may be termed an “Initiator” of theoperation, while a STA responding to the ranging/sounding or otherrequest may be termed a “Responder” of the operation.

FIG. 5A shows an example message flow 500 for ranging between anInitiator 505 (e.g. AP 240) and Responder (e.g. UE 100) 507 inaccordance with certain embodiments presented herein. For example, afirst bit in Reserved subfield 432 (FIG. 4B) may be used by Initiator505 to indicate to Responder 507 that immediately subsequent NDP frame515 is to be used for ranging. Further, NDPA frame 510 may include asingle STA Info field 435 (indicating unicast) and the RA field 420 maybe set to the address of Responder 507. Exemplary message flow 500,shown in FIG. 5A, may be consistent in some respects, for example, withspecifications, diagrams, and guidelines found in some 802.11 standards.

As shown in FIG. 5A, NDPA frame 510 may be sent by Initiator 505. NDPAframe 510 may be followed by transmission of NDP frame 515 at time T1513 after a time interval given by Short Interframe Space (SIFS) timeinterval 512 measured from the end of transmission of NDPA frame 510.Time intervals in the following figures are not shown to scale. NDPFrame 512 may be received by Responder 510 at time T2 514. Time T1 513may be captured by Initiator 505, while time T2 514 may be captured byResponder 510.

The SIFS interval, is a range of time duration values for which areprovided by relevant IEEE 802.11 standards. The SIFS interval may, forexample, specify a time to transition from a receive mode (e.g., toreceive a request or other frame) to a transmit mode (e.g., to transmitan acknowledgment or other frame).

Responder 507 may respond capturing a first time T3 at which Fine TimingMeasurement (FTM) frame 522 is transmitted. An FTM procedure may be usedfor ranging measurements, for example, for a UE (e.g. non-AP STA) toobtain its range to another STA (e.g. AP STA). FTM may be used toprovide increased timestamp resolution. In some embodiments, thetimestamp resolution may range from 10 nanoseconds to 100 picoseconds.

Further, in some embodiments, FTM frame 522 may include Angle of Arrival(AoA) and Angle of Departure (AoD) measurements, or other angularmeasurements, from the previously received NDP. In some embodiments, FTMframe 522 may be sent at a time subsequent to angular computationsperformed by the Responder 507. In some embodiments, FTM frame 522 mayoptionally include various other measured parameters as outlined furtherbelow. In some embodiments, AoA and AoD may determined (e.g. byResponder 507) based on measurements obtained during NDP and NDPA packettransmission.

After a SIFS time interval measured from the end of reception of FTMframe 522, Initiator 505 may respond with an Acknowledgement (Ack)message 532 capturing a second time T4 524 at which the FTM framearrives at Initiator 505 and a third time T5 530 at which Initiator 505transmits Ack message 532. Responder 507 may capture a fourth time T6535 at which Ack message 532 arrives at Responder 507.

In some embodiments, Responder 510 may respond to Ack message 532 withFTM frame 540, which may include times T3 520, T6 535, AoA and AoDinformation. In some embodiments, FTM frame may include Channel FeedbackInformation (CFI). In some embodiments, FTM frames 522 and 540 mayinclude CFI. CFI may facilitate computation of AoD for a multi-chaininitiator and/or computation of a more precise ranging estimate (e.g.improved determination of arrival time for the NDP frame) due to theinclusion of multi-chain information in the CFI.

After a SIFS time interval measured from the end of reception of FTMframe 540, Initiator 505 may respond to FTM frame 540 with Ack message545. In some embodiments, FTM sessions such as shown in exemplarymessage flow 500 may be used to determine RTT between Initiator 505 andResponder 507 and/or Time Difference Of Arrival (TDOA) timinginformation associated with the respective access points. In someembodiments, a position calculation unit in a UE and/or AP may determinea position of the UE based on RTT and/or TDOA information derived fromthe FTM session(s). For example, RTT may be calculated by Initiator 505based on times T3, T4, T5, and T6 by computing (T6−T3)−(T5−T4).

FTM responders may sometimes transmit an FTM frame in response to an FTMRequest. The additional FTM request that precedes the FTM frametransmission may increase overhead. Further, conventional schemestransmit FTM frames using a single antenna, which may limit calculationof various ranging parameters related to transmission modes. Moreover,when a single antenna is used for transmission, the types of parametersthat can be measured may be limited and/or measurement accuracy maysuffer. For example, if AoA is measured and/or determined based ontransmission from a single antenna, the measurement may be inaccuraterelative to AoA measured/determined from multiple antenna transmissions.In some embodiments disclosed herein, FTM frames may be transmittedusing multiple antennas thereby facilitating: (i) accurate computationof various parameters, (ii) in multiple transmission modes. In someembodiments, NDP frames, which may be transmitted using multipleantennas, may facilitate measurement of AoA, AoD, and/or various otherparameters, as outlined further below.

FIG. 5B shows an example unicast message flow 550 between an Initiator552 (e.g. AP 240) and a responder identified as Responder 554 (e.g.non-AP STA/UE 100), in accordance with certain embodiments presentedherein. For example, a first bit in Reserved subfield 432 (FIG. 4B) maybe used by Initiator 552 to indicate to Responder 554 that immediatelysubsequent NDP frame 572 is to be used for ranging. Further, NDPA frame555 may include a single STA Info field 435 (indicating unicast) and theRA field 420 may be set to the address of Responder 554.

As shown in FIG. 5B, NDPA frame 555 may be unicast by Initiator 552.NDPA frame 555 may be followed by transmission of frame 572 at time T1570 after a time interval given by SIFS 565 measured from the end oftransmission of NDPA frame 555. As shown in FIG. 5B, frame 572 may takethe form of one of: an NDP_az frame, or an NDP frame, or a BeamRefinement Protocol (BRP) frame.

Responder 554 may capture a first time T2_1 560 at which NDP frame 555is received and a second time T3_1 575 at which the CBF frame is sent.CBF frame 580 may be sent at time T3_1 575 after a time interval givenby SIFS measured from the end of reception of frame 572.

In some embodiments, CBF frame 580 may include CFI shown as CFI1 andtimes T2_1 560 and T3_1 575, or its difference. In some embodiments,Initiator 552 may capture the time T4_1 572 at which CBF frame 580 isreceived. Conventionally, CBF frames may include angles associated withbeamforming matrices. In some embodiments described herein, CBF framesmay alternatively (or additionally) include CFI1. Initiator 552 maydetermine an AoD or Location Configuration Information (LCI) from CFI1transmitted in CBF frame 580. LCI determined from CFI1 may includelocation information such as latitude/longitude information of Responder554.

In some embodiments, Responder 554 may determine an AoD based on NDPframe 572 and/or calibration data from Initiator 552. In someembodiments, Responder 554 may also determine an LCI (e. g.latitude/longitude) from previously acquired location information (e.g.information from a beacon frame) from Initiator 552.

In some embodiments, Initiator 552 may further respond with FTM No Ackframe 578 including time T1 570, time T4_1 572, AoD, and LCI. As usedherein, an “FTM No Ack” frame may take the form of an FTM frame with anacknowledgment response field, bit or other indication that a responseto the “FTM No Ack” frame may be sent in the form of an FTM frame, whichis referred to herein as an “FTM Ack” frame. When the acknowledgmentresponse field or bit is not set, a regular Ack frame may sent inresponse to the FTM No Ack frame. In some embodiments, a regular Ackframe may sent in response to the FTM No Ack frame, when the responderlack the capability for an “FTM Ack” response. For clarity and ease ofdescription, the acknowledgment response field, bit or other indicationis also referred to herein as an “FTM Ack” bit.

In conventional exchanges, FTM frames are responded to with anAcknowledgement (Ack) frame (e.g. Ack frame 532 in FIG. 5A). In someembodiments, setting a bit termed the “FTM Ack” bit to 1 in a FTM No Ackframe, may be used to indicate that a conventional Ack frame response isnot desired. In some embodiments, the response to an FTM No Ack framemay take the form of an FTM Ack frame, which may be of a format similarto that of an FTM frame.

In some embodiments, the FTM frame may be augmented with an “FTM Ack”bit, which is set to 1 in FIG. 5B. The FTM Ack bit may be used toindicate that the receiver of FTM No Ack frame 578 with FTM Ack=1 mayrespond with an FTM Acknowledgement (FTM Ack) frame such as FTM Ackframe 579.

In some embodiments, upon receipt of FTM No Ack frame 578 with FTMAck=1, Responder 554 may respond after a SIFS interval with FTM Ackframe 579 including time T2_1 560 and time T3_1 575. In someembodiments, the Round Trip Time between Initiator 552 and Responder 554may be calculated, for example, as RTT=(T4_1−T1)−(T3_1−T2_1) byInitiator 552 and/or Responder 1 554.

Existing CBF structure supports a maximum of: 8 streams (56 angles), 468subcarriers, and 8 bits per tone on average. Thus, the CBF may hold(468*56)/(2*8/8)=13.1K bytes of information, which may support somemulti-antenna embodiments described herein.

FIG. 5C shows the amount of CFI data that may be transmitted from atransmitting STA to a receiving STA for different antennaconfigurations. In some embodiments, a CFI information element/field maybe added or incorporated as an optional sub-element to the current FTMframe definition. In some embodiments, the CFI field may be structuredin a manner similar to a Channel State Information (CSI) Report field asdefined in various specifications. For example, the structure of the CFIfield may mirror the structure of the CSI Report field as defined in theWLAN MAC & PHY Specifications (e.g. Table 9-52, § 9.4.1.28).

FIG. 5D shows the format of a VHT MIMO Control field 547, which may formpart of a Compressed Beamforming Feedback (CBF) frame 547. VHT MIMOControl field 547 includes Reserved bits 586, which are bits B16 and B17in the VHT MIMO control field. In some embodiments, for example, when NcIndex subfield 557=7 (Nc=8), and Nr Index subfield 567=7 (Nr=8), ChannelWidth subfield 577=3 (160 MHz or 80+80 MHz), Grouping subfield 587=0(Ng=1, no grouping), Codebook Information subfield 588=1, and Feedbacktype subfield 589=0 (single user) or 1 (multi user), then, Reserved bits586 may be used to indicate that the CBF frame is being used forranging/RTT purposes. In some embodiments, Grouping subfield 587=3(which is reserved) may also be used to indicate that the CBF frame isbeing used for ranging/RTT purposes (e.g. as shown in FIG. 5B).

FIG. 5E shows a unicast message flow 590 with NDPA 593 announcing asubsequent frame (NDP_az, NDP, or BRP) for ranging according to somedisclosed embodiments. As shown in FIG. 5E, NDPA frame 593 may beunicast by FTM Initiator 591 at time T1 583. NDPA frame 593 may befollowed by transmission of frame 594 at time T1′ 595 after a timeinterval given by Short Interframe Space (SIFS) 565 measured from theend of transmission of NDPA frame 593.

Further, as shown in FIG. 5E, frame 594, which follows NDPA frame 593,may take the form of one of: an NDP_az frame with time T1 591, or an NDPframe, or a Beam Refinement Protocol (BRP) frame.

FTM Responder 592 may capture a first time T2 599 at which NDPA frame593 is received, and a second time T2′ 596 at which frame 594 isreceived and a third time T3 597 at which FTM frame 595 is received. FTMframe 595 may include time T2 599, time T2′ 596. CFI, and time T3 597.As shown in FIG. 5E, FTM frame 595 may be sent after a SIFS timeinterval following the end of reception of frame 594.

When FTM Initiator 591 and FTM Responder 592 are synchronized the Timeof Flight may be calculated as: (a) the difference of times T2 599 andT1 583, (T2−T1); or (b)

$\frac{\left( {{T\; 2} - {T\; 1}} \right) + \left( {{T\; 2^{\prime}} - {T\; 1^{\prime}}} \right)}{2}.$When FTM Initiator 591 and FTM Responder 592 are not synchronized, theTOF is:

${TOF} = {\frac{RTT}{2} = {\frac{\left( {{T\; 4} - {T\; 1^{\prime}}} \right) + \left( {{T\; 3} - {T\; 2^{\prime}}} \right)}{2}.}}$

In some embodiments, FTM Initiator 591 may respond to FTM frame 595 withAcknowledgement (Ack) frame 595A.

FIG. 6 shows an example message flow 600 between FTM Initiator 605 (e.g.AP 240) and two FTM responders FTM Responder 1 610 and FTM Responder 2615 (e.g. UEs 100-1 and 100-2), where an NDPA is broadcast to both FTMResponder 1 and FTM Responder 2.

As shown in FIG. 6, NDPA frame 620 may be broadcast or multicast by FTMInitiator 605. For example, a first bit in Reserved subfield 432 (FIG.4B) may be used by FTM Initiator 605 to indicate to Responder 507 thatimmediately subsequent NDP frame 515 is to be used for ranging. Forexample, NDPA frame 620 may include multiple STA Info fields 435 (FIG.4A) to indicate broadcast and the RA field 420 (FIG. 4A) may be set tothe broadcast address. NDPA frame 620 may be followed by transmission ofNDP frame 625 at time T1 624 after a time interval given by SIFS 622measured from the end of transmission of NDPA frame 620.

FTM Responder 1 610 may capture a first time T2_1 626 at which NDP frame625 is received by FTM Responder 1 610 and a second time T3_1 636 atwhich Compressed Beamforming Feedback (CBF) frame 630 is sent by FTMResponder 1 610. In some embodiments, CBF frame 630 may be sent by FTMResponder 1 610 after a time interval given by SIFS from the receptionof NDP frame 625. In some embodiments, appropriate reserved bits 586(FIG. 5D) in VHT MIMO control field (FIG. 5D) may be set in CBF framesto indicate that the CBF frame is being used for ranging/RTT purposes.In some embodiments, CBF frame 630 may include CFI of FTM Responder 1(CFL1). In some embodiments, FTM Initiator 605 may capture the time T4_1632 at which CBF frame 630 is received.

Further, FTM Responder 2 615 may capture a first time T2_2 628 at whichNDP frame 625 is received by FTM Responder 2 615 and a second time T3_2634 at which Compressed Beamforming Feedback (CBF) frame 640 is sent byFTM Responder 2 615. In some embodiments, CBF frame 640 may be sent byFTM Responder 2 615 after a time interval given by SIFS from thereception of NDP frame 625 at Responder 2. In some embodiments, CBFframe 640 may include CFI of FTM Responder 2 (CFI_2). In someembodiments, FTM Initiator 605 may capture the time T4_2 642 at whichCBF frame 630 is received.

In some embodiments, FTM Responder 1 610 may further respond with FTM NoAck frame 644 including times T2_1 626 and T3_1 636. FTM No Ack frame644 may be augmented with an “FTM Ack” bit, which is set to 1 in FIG.6A. The FTM Ack bit may be used to indicate that the receiver of FTMframe 644 with FTM Ack=1 may respond with an FTM Acknowledgement (FTMAck) frame such as FTM Ack frame 645. In some embodiments, upon receiptof FTM No Ack frame 644 with FTM Ack=1, Initiator 605 may respond withFTM Ack frame 645 including times T1 624 and T4_1 632. In someembodiments, RTT1=(T4_1−T1)−(T3_1−T2_1), where RTT1 is the RTT betweenInitiator 605 and Responder 1 610. RTT1 may be calculated by Initiator605 and/or Responder 1 610. In some embodiments, the FTM Ack frame maybe of a similar or the same format as an FTM frame.

In some embodiments, Responder 2 615 may further respond with FTM No Ackframe 646 including times T2_2 628 and T3_2 634. FTM No Ack frame 646may be augmented with an “FTM Ack” bit, which is set to 1 in FIG. 6A.The FTM Ack bit may be used to indicate that the receiver of FTM frame646 with FTM Ack=1 may respond with an FTM Acknowledgement (FTM Ack)frame such as FTM Ack frame 647. In some embodiments, upon receipt ofFTM No Ack frame 646 with FTM Ack=1, Responder 2 615 may respond withFTM Ack frame 647 including times T1 624 and T4_2 642. In someembodiments, RTT2=(T4_2−T1)−(T3_2−T2_2), where RTT2 is the RTT betweenInitiator 605 and Responder 2 615. RTT2 may be calculated by Initiator605 and/or Responder 2 615.

In some embodiments, an order or priority scheme may be establishedamong responders to facilitate responses by multiple responders to NDPAframe 620 and NDP frame 625. In general, in an environment with kresponders, the RTT for the k^(th) responder may be calculated as(T4_k−T1)−(T3_k−T2_k), where: T4_k is the time of reception of CBF framefrom the k^(th) responder at Initiator 605; T2_k is the time ofreception of NDP frame 625 at the k^(th) responder; and T3_k is the timeat which the CBF frame from the k^(th) responder is transmitted. Asoutlined above, the CBF frame from the k^(th) responder may include CFIfor Responder k (CFIk).

FIG. 7A shows an example message flow 700 between Initiator 705 (e.g. AP240) and two responders Responder 1 710 and Responder 2 715 (e.g. UEs ornon-AP STAs 100-1 and 100-2), where an NDPA is broadcast/multicast toresponders Responder 1 and Responder 2.

As shown in FIG. 7A, NDPA frame 720 may be broadcast by Initiator 705.NDPA frame 720 may be followed by transmission of NDP frame 725 at timeT1 724 after a time interval given by SIFS 722 measured from the end oftransmission of NDPA frame 720.

Responder 1 710 may capture a first time T2_1 726 at which NDP frame 725is received by Responder 1 710 and a second time T3_1 736 at whichCompressed Beamforming Feedback (CBF) frame 730 is sent by Responder 1710. In some embodiments, CBF frame 730 may be sent by Responder 1 710after a time interval given by SIFS from the end of reception of NDPframe 725. In some embodiments, Reserved bits 586 (FIG. 5D) may be usedto indicate that the CBF frame is being used for ranging/RTT purposes.In some embodiments, CBF frame 730 may include one CFI of Responder 1(CFL1) In some embodiments, Initiator 705 may capture the time T4_1 732at which CBF frame 730 is received.

In some embodiments, Initiator 1 705 may send a Beamforming Report Pollframe 738, with a Basic Service Set IDdentifier (BSSID) associated withResponder 2 715. The BRP frame may be used to obtain a beamformingreport (such as a Very High Throughput (VHT) beamforming report) from aprior sounding. Responder 2 715 may capture a first time T2_2 728 atwhich BRP frame 738 is received by Responder 2 715 and a second timeT3_2 734 at which CBF frame 740 is sent by Responder 2 715. In someembodiments, CBF Trigger frame 740 may be sent by Responder 2 715 aftera time interval given by SIFS from the end of reception of CBF Triggerframe 738 at Responder 2 715. In some embodiments, CBF frame 740 mayinclude one of CFI of Responder 2 (CFI_2). In some embodiments,Initiator 705 may capture the time T4_2 742 at which CBF frame 730 isreceived.

In some embodiments, Responder 1 710 may further respond with FTM No Ackframe 744 including times T2_1 726 and T3_1 736. FTM No Ack frame 744may be augmented with an “FTM Ack” bit, which is set to 1 in FIG. 7A.The FTM Ack bit may be used to indicate that the receiver of FTM frame744 with FTM Ack=1 may respond with an FTM Acknowledgement (FTM Ack)frame such as FTM Ack frame 745. In some embodiments, upon receipt ofFTM No Ack frame 744 with FTM Ack=1, Responder 1 710 may respond withFTM Ack frame 745 including times T1 724 and T4_1 732. In someembodiments, RTT1=(T4_1−T1)−(T3_1−T2_1), where RTT1 is the RTT betweenInitiator 705 and Responder 1. Since both Initiator 705 and Responder 1710 have sufficient timestamp information, RTT1 may be calculated byInitiator 605 and/or Responder 1 710.

In some embodiments, Responder 2 715 may further respond with FTM No Ackframe 746 including times T2_2 728 and T3_2 734. FTM No Ack frame 746may be augmented with an “FTM Ack” bit, which is set to 1 in FIG. 7A.The FTM Ack bit may be used to indicate that the receiver of FTM frame746 with FTM Ack=1 may respond with an FTM Acknowledgement (FTM Ack)frame such as FTM Ack frame 747. In some embodiments, upon receipt ofFTM No Ack frame 746 with FTM Ack=1, Responder 2 715 may respond withFTM Ack frame 747 including times T1 724 and T4_2 742. In someembodiments, RTT2=(T4_2−T1)−(T3_2−T2_2), where RTT2 is the RTT forResponder 2 and may be calculated by Initiator 705 and/or Responder 2715.

In some embodiments, a Beamforming Report Poll frame may be sent byInitiator 705 to each Responder_k thereby facilitating responses bymultiple responders to NDPA frame 720 and NDP frame 725. In general, inan environment with k responders, the RTT for the k^(th) responder,given by RTT_k, may be calculated as: RTT_k=(T4_k−T1)−(T3_k−T2_k),where: T4_k is the time of reception of CBF frame from the k^(th)responder at Initiator 705; T2_k is the time of reception of thecorresponding k^(th) BRP frame at the k^(th) responder; and T3_k is thetime at which the CBF frame from the k^(th) responder is transmitted. Asoutlined above, the CBF frame from the k^(th) responder may include CFIof Responder_k (CFI_k).

FIG. 7B shows a format for an example Beamforming Report Poll frame inaccordance with certain embodiments presented herein. In someembodiments, Beamforming Report Poll frame may include Frame Controlfield 752; Duration Field 754; RA (Recipient Address) field 756, whichis set to the address of the intended recipient; TA (TransmitterAddress) field 756, which may be set to the address of the STAtransmitting the CBF Trigger; and Feedback Segment Retransmission Bitmapfield 762, which indicates the requested feedback segments of a VeryHigh Throughput (VHT) or HEW.

FIGS. 8A and 8B show an example Fine Timing Measurement (FTM) frame 800,which may include AoA, AoD, and/or other information in accordance withcertain embodiments presented herein. In some embodiments, FTM No Ackframe and FTM Ack frames may take the form of FTM frame 800 withappropriate values of bits or fields in FTM frame 800. Accordingly, FTMframe 800 may be used in conjunction with the FTM, Ack, FTM No Ack, andFTM Ack message sequences/exchanges described herein.

As shown in FIG. 8A, FTM frame 800 may include fields Category 802,Public Action 804, Dialog Token 806, Follow Up Dialog Token 608, Time ofDeparture (TOD) 810, Time of Arrival (TOA) 812, TOD Error 814, TOA Error816. FTM frame 800 may optionally include one or more of: FTMSynchronization Information 818, LCI Report 820 field, Location CivicReport field 822, and Fine Timing Measurement parameters field 824,which may be of variable length. The above fields are defined in theWLAN MAC & PHY Specifications.

Public Action 804 differentiates various Public Action frame formats.provides a mechanism for specifying various extended management actions.A values of 32 indicates an FTM Request, while a value of 33 indicatesan FTM frame. Category 802 may specify a category of Public Action 804.For example, a Category value of 21 may indicate VHT. Dialog Token 806may be a nonzero value chosen by a responding STA to identify an FTM NoAck/FTM frame as the first of a pair, with a second or follow-up FTMframe to be sent later. The Dialog Token field may be set to 0 toindicate the end of the FTM session.

The second or follow-up FTM frame of the pair may use the nonzero valueof Dialog Token 806 in the last transmitted FTM frame in Follow UpDialog Token 808 to indicate that: (i) the current (second) FTM/FTM Ackframe (of the pair) is a follow up FTM, and, (ii) TOD 810, TOA 812, TODError 814, and TOA Error 818 fields contain the values associated withtimestamps captured with the first FTM/FTM No Ack frame of the pair.Follow Up Dialog Token 808 may be set to 0 to indicate that: (i) thecurrent FTM/FTM No Ack frame is not a follow up; and (ii) TOD 810, TOA812, TOD Error 814, and TOA Error 818 fields are reserved. TOD and TOAfields may be expressed in units of picoseconds.

In some embodiments, TOD 810 may include a timestamp that represents thetime, with respect to a time base, at which the start of the preamble ofthe last transmitted FTM No Ack/FTM frame appeared at a transmit antennaconnector of a transmitting STA.

In some embodiments, TOA 812 field may include a timestamp thatrepresents the time, with respect to a time base, at which the start ofthe preamble of an FTM Ack/Ack frame to the last transmitted FTM NoAck/FTM frame arrived at the receive antenna connector of a receivingSTA.

In some embodiments, FTM Synchronization Information 818 is present inthe initial FTM frame and in any retransmissions.

FIG. 8B shows the format of example AoA field 830, while FIG. 8C showsthe format of example AoD field 840 according to certain embodimentsdisclosed herein. In some embodiments, AoA field 830 may include ElementID 832, Length 834, and AoA information 848. Similarly. in someembodiments, AoD field may include Element ID 842, Length 844, AoDinformation 848. In some implementations, the AoA Information may storevalues for Theta_AoA and Phi_AoA, as described below, in FIG. 8F toindicate angle of arrival information of a specified frame. In someimplementations, the AoD field may store values for Theta_AoD andPhi_AoD to indicate angle of departure information of the specifiedframe.

In one embodiment, the TOD field 810 may include 6 bytes, the TOA field812 may include 6 bytes, the AoA field (e.g. as a separate optional AoAfield 830, or as part of FTM Parameters 824) may include 5 bytes, andthe AoD field 613 (e.g. as a separate optional AoD field 840, or as partof FTM Parameters 824) may include 5 bytes (although for otherembodiments, other field lengths may be used).

In some embodiments, AoA field 830 may include AoA information 838 forframes exchanged during a ranging operation, and the AoD field 840 mayinclude AoD information 848 for frames exchanged during the rangingoperation. For example, a responder may embed AoA information 838 intoAoA field 830 (or another information element) serving as an AoA fieldof FTM frame 800, and may embed AoD information 848 of the FTM frameinto AoD field 840 (or another information element serving as an AoDfield of FTM frame 800). The responder device may also embed TOAinformation into the TOA field 812 of FTM frame 800, and may embed TODinformation of into the TOD field 810 of FTM frame 800. The responderSTA may then use the FTM frame 800 as an FTM No Ack frame rangingoperations to transmit angle information (e.g., AoD and/or AoA) and timevalues to the initiator device. In some embodiments, in part, FTM No Ackframe may be compliant with existing standards/formats for FTM frames,thereby facilitating use of the frames in environments with a mix oflegacy devices and devices that support the embedding, transmission andreception, of AoA, AoD, and other information in FTM (FTM No Ack) and/orFTM Ack frames.

In some embodiments, Element ID field 842 may store an element ID valueindicating that AoA field 830 includes AoA information for a specifiedframe, while Length field 834 may store a value indicating a length (inbytes) of AoA field 830. In some embodiments, Element ID field 842 maystore an element ID value indicating that AoD field 840 includes AoDinformation for a specified frame, while Length field 844 may store avalue indicating a length (in bytes) of AoD field 840.

FIG. 8D shows a portion 850 of an example Fine Timing Measurement(FTM)/FTM No Ack frame 800 indicating that a response may be sent as anFTM Acknowledgement (FTM Ack) frame. In some embodiments, a reserved bitin the FTM/FTM No Ack frame 800 may be set to indicate to a responderthat a response with an FTM Ack frame is desired. In some embodiments,bit B15 870 of the Max TOA Error Field 860 may be used to indicate to aresponder that a response with an FTM Ack frame is desired. The reservedbit (e.g. bit B15 870 of the Max TOA Error Field 860) in an FTM No Ackframe 800, which is used to indicate to a responder that a response withan FTM Ack frame is desired, is also referred to as an acknowledgmentresponse bit herein.

FIG. 8E is an example 3-dimensional coordinate system 880 forrepresenting the position of a STA using a radius “r” and angles “theta”and “phi.” As depicted in FIG. 8A, phi may be an angle with respect tothe horizontal (x-y) plane, while theta may be an angle with respect tothe vertical (z) axis. Phi may range from 0° to 360°, while theta mayrange from 0° to 180°. The radius r is the distance between the originand a point coordinate (r, θ, and φ) representing the location of awireless device relative to the origin. In some implementations, the AoAfield may store values for Theta_AoA and Phi_AoA to indicate angle ofarrival information of a specified frame. In some implementations, theAoD field may store values for Theta_AoD and Phi_AoD to indicate angleof departure information of the specified frame.

Thus, disclosed embodiments include the use of FTM frame 800, which, insome embodiments, may take the form of a conventional FTM frame. In someembodiments, FTM frame 800 may include AoA, AoD and other information.For example, FTM Measurement parameter 824, additional optional AOAand/or AoD fields, may comprise AoA, AoD, and/or other parameters. Insome embodiments, FTM Measurement Parameters 824 may be used to carryinformation pertaining to AoA, AoD, and/or other parameters.

In some embodiments, separate optional AoA and/or AoD fields may beprovided in FTM frame 800. The AoA and/or AoD fields may carry AoAand/or AoD information. FTM frame 800 may include other bits, fields etcto indicate when FTM frame 800 includes additional information. In someembodiments, the AoA, AoD, FTM Ack and other information may be includedin a manner so that legacy devices may continue to function normally.For example, in some embodiments, where the responder device may be anaccess point STA, the responder device may embed, into a beacon or otherframe, information indicating whether the responder device is capable ofincluding AoA and/or AoD information in one or more frames exchangedbetween the initiator device and the responder device. In some aspects,this information may be embedded within an information element (IE) or avendor-specific information element (VSIE) of the beacon frame or otherframe.

Further, in some embodiments, FTM frame 800 may (alternatively oradditionally) take the form of an FTM No Ack or FTM Ack frame. Forexample, as shown in FIG. 8C, a reserved bit or acknowledgment responsebit in the FTM No Ack frame 800 may be set to indicate to a responderthat a response with an FTM Ack frame is desired.

In some embodiments, the first 12 bits of the AoA information field 838may be used to indicate a value for Theta_AoA, and the second 12 bits ofthe AoA information field may be used to indicate a value for Phi_AoA.Similarly, the first 12 bits of the AoD information field 848 may beused to indicate a value for Theta_AoD, and the second 12 bits of theAoD information field 848 may be used to indicate a value for Phi_AoD.In embodiments, where 12-bit values are used, the 12-bit values forTheta_AoA and Theta_AoD may provide a resolution of approximately 0.044°(180° divided by (212−1)), while the 12-bit values for Phi_AoA andPhi_AoD may provide a resolution of approximately 0.088° (360° dividedby (212−1)).

FTM frames formatted according to current FTM protocols (e.g., asdefined by the IEEE 802.11REVmc standards) include a 6-byte TOD field810 and a 6-byte TOA field 812 to store TOD and TOA information,respectively—e.g. to embed timestamp values t_(1_TOD) and t_(2_TOA),where t_(1_TOD) is the time of departure of a first frame, and t_(2_TOA)is the time of arrival of a corresponding response frame, where thefirst frame and corresponding response frame are used to measure RTT. Insome embodiments, because RTT may be determined using a single timedifference value (t_(2_TOA)−t_(1_TOD)) rather than two individualtimestamp values (e.g., one of the TOD 810 or TOA 812 fields may berepurposed to store AoA and AoD information, thereby eliminating theneed for an FTM frame to include a separate field that stores AoA andAoD information (and thus reducing the size of the FTM frame). Forexample, as indicated above, RTT may be determined as(t_(2_TOA)−t_(1_TOD)), where t_(1_TOD) is the time of departure of afirst frame, and t_(2_TOA) is the time of arrival of a correspondingresponse/acknowledgment frame, where the first frame and correspondingresponse frame are used for ranging, including measuring RTT.

FIG. 9A shows an example symmetric message flow between an initiator(e.g. AP 240) and a responder (e.g. UE 100). For example, a first bit inReserved subfield 432 (FIG. 4B) in NDPA frame 912 may be used byInitiator 905 to indicate to Responder 910 that immediately subsequentNDP frame 918 is to be used for ranging. Further, a second bit inReserved subfield 432 (FIG. 4B) in NDPA frame 912 may be used byInitiator 905 to indicate to Responder 910 that Initiator 905 can shareranging information.

As shown in FIG. 9A, NDPA frame 912 may be sent by Initiator 905. NDPAframe 912 may be followed by transmission of NDP frame 918 at time T1920 after a time interval given by SIFS 914 measured from the end oftransmission of NDPA frame 912. Initiator 905 may record the time oftransmission of NDP frame 912 at time T1 920. Responder 910 may recordthe time of reception of NDP frame 912 at time T2 916.

Further, as shown in FIG. 9A, NDPA frame 922 (e.g. with broadcast bit inReserved subfield 432 set to 1) may be sent by Responder 910. Forexample, a first bit in Reserved subfield 432 (FIG. 4B) in NDPA frame922 may be used by Responder 910 to indicate to Initiator 905 thatimmediately subsequent NDP frame 925 is to be used for ranging. Further,a second bit in Reserved subfield 432 (FIG. 4B) in NDPA frame 922 may beused by Responder 910 to indicate to Initiator 905 to that Responder 910can share ranging information.

NDPA frame 922 may be followed by transmission of NDP frame 925 at timeT3 924 after a time interval given by SIFS measured from the end oftransmission of NDPA frame 922. Responder may record the time oftransmission of NDP frame 925 at time T3 924. Initiator 905 may recordthe time of reception of NDP frame 925 at time T4 926.

Responder 910 may respond to NDP frame 918 with FTM frame 928, which mayinclude time T2 916, time T3 924, and the CFI. Initiator 905 may respondwith an Acknowledgement (Ack) message 930. Further, Initiator 904 mayrespond to NDP frame 925 with FTM frame 932, which may include time T1920, time T4 926, and the CFI. Responder 910 may respond with anAcknowledgement (Ack) message 934. In some embodiments, RTT, TDOA,and/or other calculations may be performed by Initiator 905 and/orResponder 910 based on the recorded and received information.

In some embodiments, instead of sending of FTM frame 928 (as shown inFIG. 9A), Responder 910 may send a FTM No Ack frame with FTM Ack bit setto 1 with time T2 916, time T3 924, and the CFI; and Initiator 905 mayrespond with an FTM Ack frame (instead of Ack frame 930) including timeT1 920, time T4 926, and the CFI. Thus, Ack frames 930 and 934 may beobviated thereby speeding up the exchange of information for RTT, TDOA,and/or other calculations related to the FTM sessions.

FIG. 9B shows an example message flow between an initiator (e.g. AP 240)and a responder (e.g. UE 100).

As shown in FIG. 9B, NDPA frame 942 may be sent by Initiator 945 at timeT1 941. NDPA frame 942 may be followed by transmission of frame 944 attime T1′ 942 after a time interval given by SIFS 914 measured from theend of transmission of NDPA frame 942. Initiator 945 may record the timeof transmission T1 of NDPA frame 942 and the time of transmission T1′ offrame 944. In some embodiments, frame 944 may be one of: an NDP_az framewith time T1 947, or an NDP frame 944 or a Beam Refinement Protocol(BRP) frame. NDPA frame 942 may be received by Responder 950 at time T2943, while frame 944 may be received by Responder 950 at time T2′ 949.

Responder 950 may respond to frame 942 with FTM No Ack frame 948. FTM NoAck frame 948 may have FTM Ack bit set to 1. FTM No Ack frame 948 mayinclude time T2 943, time T2′ 949, CFI, and time T3 948 information.Responder 950 may record the time T3 946 of transmission of FTM No Ackframe 948. In some embodiments, FTM No Ack frame 948 may request AoD,AoA, Azimuth, or Range information.

In some embodiments, an FTM request frame may be used, alternatively, torequest AoD, AoA, Azimuth, or Range information. In embodiments where anFTM Request frame requesting AoD, AoA, Azimuth, and/or Range informationis sent instead of a FTM No Ack frame, then, an Ack frame may be sent byResponder 950 (instead of an FTM ACK frame).

Initiator 945 may record the time T4 952 of arrival of FTM Ack frame948. Initiator 945 may respond with FTM Ack frame 956, which includes anACK. In some embodiments, FTM ACK frame 956 may include one or more ofAoD, AoA, Azimuth, and Range information. In some embodiments,information included in FTM ACK frame 956 may be based, in part, oninformation requested in FTM frame 948. Responder 950 may record thetime T6 958 of arrival of Ack message 956.

When Initiator 945 and Responder 950 are synchronized the Time of Flightmay be calculated as: (a) the difference of times T2 943 and T1 941,(T2−T1); or (b)

$\frac{\left( {{T\; 2} - {T\; 1}} \right) + \left( {{T\; 2^{\prime}} - {T\; 1^{\prime}}} \right)}{2}.$When Initiator 945 and Responder 950 are not synchronized, the TOF maybe calculated as

${TOF} = {\frac{RTT}{2} = {\frac{\left( {{T\; 4} - {T\; 1^{\prime}}} \right) + \left( {{T\; 3} - {T\; 2^{\prime}}} \right)}{2}.}}$

FIG. 9C shows an example symmetric message flow between an initiator(e.g. AP 240) and a responder (e.g. UE 100) where an NDPA announces asymmetric request.

As shown in FIG. 9C, NDPA frame 972 may be sent by Initiator 975. NDPAframe 972 may be followed by transmission of NDP frame 976 at time T1974 after a time interval given by SIFS 973 measured from the end oftransmission of NDPA frame 972. For example, a first bit in Reservedsubfield 432 (FIG. 4B) may be used by Initiator 975 to indicate toResponder 980 that immediately subsequent NDP frame 976 is to be usedfor ranging. Further, NDPA frame 972 may include a single STA Info field435 (indicating unicast) and the RA field 420 may be set to the addressof Responder 980. Initiator may record the time of transmission of NDPframe 972 at time T1. Responder 980 may record the time of reception ofNDP frame 972 at time T2 978.

Further, as shown in FIG. 9C, NDPA frame 984 may be sent by Responder980. NDPA frame 984 may be followed by transmission of NDP frame 988 attime T3 982 after a time interval given by SIFS measured from the end oftransmission of NDPA frame 984. For example, a first bit in Reservedsubfield 432 (FIG. 4B) in NDPA frame 984 may be used by Responder 980 toindicate to Initiator 975 that immediately subsequent NDP frame 988 isto be used for ranging. Further, a second bit in Reserved subfield 432(FIG. 4B) in NDPA frame 984 may be used by Responder 980 to indicate toInitiator 975 to that Responder 980 can share ranging information.Responder 980 may record the time of transmission of NDP frame 988 attime T3 982. Initiator 975 may record the time of reception of NDP frame988 at time T4 986.

Responder 980 may respond to NDP frame 976 with FTM frame 990, which mayinclude time T2 978, time T3 982, AoA, and AoD. Initiator 975 mayrespond with Acknowledgement (Ack) message 992. Further, Initiator 975may respond to NDP frame 988 with FTM frame 994, which may include timeT1 974, time T4 986, AoA, and AoD. Responder 980 may respond with Ackmessage 996. In some embodiments, RTT, TDOA, and/or other calculationsmay be performed by Initiator 975 and/or Responder 980 based on therecorded and received information.

In some embodiments, instead of sending of FTM frame 990 (as shown inFIG. 9C), Responder 980 may send a FTM No Ack frame with FTM Ack bit setto 1 with time T2 978, time T3 982, AoA, and AoD, and Initiator 975 mayrespond with an FTM Ack frame (instead of Ack message 992) includingtime T1 974, time T4 986, AoA, and AoD. Thus, Ack messages 992 and 996may be obviated thereby speeding up the exchange of information for RTT,TDOA, and/or other calculations related to the FTM sessions.

FIG. 10 shows a multicast non-symmetric message flow 1000 with multipleFTM initiators where the FTM Responder does not share information. Forexample, a first bit in Reserved subfield 432 (FIG. 4B) in NDPA frame1020 may be used by FTM Responder 1015 to indicate to FTM Initiatorsthat the immediately subsequent frame 1040 is to be used for ranging.Further, a second bit in Reserved subfield 432 (FIG. 4B) in NDPA frame1020 may be used by FTM Responder 1015 to indicate to FTM Initiators tothat FTM Responder 1015 does not share ranging information. As shown inFIG. 10, NDPA frame 1020 may be sent by FTM Responder 1 1015 at time T11025. FTM Responder 1 1015 may record the time of transmission of NDPAframe at time T1 1025. NDPA frame 1020 may be received by FTM Initiator1 1010 at time T2 1030. Time T2 1030 may be recorded by FTM Initiator1010.

NDPA frame 1020 may be followed by transmission (by FTM Responder 11015) of frame 1040 at time T1_1 1035 after a time interval given bySIFS measured from the end of transmission of NDPA frame 1020. Frame1040 may take the form of an NDP_az frame with time T1_1 1035, an NDPframe, or a Beam Refinement Protocol (BRP) frame. Frame 1040 may bereceived by FTM Initiator 1 1010 at time T2_1 1045. Time 2_1 1045 may berecorded by FTM Initiator 1 1010.

After a SIFS interval following the end of reception of frame 1040, attime T3_1 1055, FTM Initiator 1 1010 may transmit CBF 1060 with the CFIof Responder 1 CFL_1, time T2_1 1045, and time T3_1 1055. CBF 1060 maybe received by FTM Responder 1 1015 at time T4_1 1065.

After a SIFS time interval, FTM Responder 1 1015 may transmitBeamforming Report Poll (BSSID k) frame 1090 with the BSSID of FTMInitiator k 1005, where k≥2 is some integer. FTM Initiator k 1005 mayreceive Beamforming Report Poll (BSSID k) frame 1090 at time T2_k 1050.After a SIFS interval following the end of reception of frame 1090, attime T3_k 1085, FTM Initiator k 1005 may transmit CBF 1075 with CFI_k,time T2_k 1050, and time 3_k 1075. CBF 1070 may be received by FTMResponder 1 at time T4_k 1080. In some embodiments, as shown in themessage exchange in FIG. 10, time T4_k 1080 may not be sent to FTMInitiator k.

FIG. 11 shows a multicast symmetric message flow 1100 with multipleinitiators where the FTM Responder shares information. As shown in FIG.11, NDPA frame 1120 may be sent by FTM Responder 1 1115 at time T1 1125.FTM Responder 1 may record the time of transmission of NDPA frame attime T1 1125. NDPA frame 1120 may be received by FTM Initiator 1 1110 attime T2 1130. Time T2 1130 may be recorded by FTM Initiator 1110.

NDPA frame 1120 may be followed by transmission (by FTM Responder 11115) of frame 1140 at time T1_1 1135 after a time interval given bySIFS measured from the end of transmission of NDPA frame 1120. Frame1140 may take the form of an NDP_az frame with time T1_1 1135, an NDPframe, or a BRP frame. Frame 1140 may be received by FTM Initiator 11110 at time T2_1 1145. Time 2_1 1145 may be recorded by FTM Initiator 11110.

After a SIFS interval following the end of reception of frame 1140, attime T3_1 1155, FTM Initiator 1 1110 may transmit CBF 1160 with CFL1,time T2_1 1145, and time T3_1 1155. CBF 1160 may be received by FTMResponder 1 1115 at time T4_1 1165.

After a SIFS time interval, FTM Responder 1 1115 may transmitBeamforming Report Poll (BSSID k, T4_(k−1)) frame 1190 with the BSSID ofFTM Initiator k 1105, where k≥2 is some integer, and T4_k. For example,after a SIFS time interval, FTM Responder 1 1115 may transmitBeamforming Report Poll (BSSID k=2, T4_1) frame 1190 with the BSSID ofFTM Initiator k=2 and T4_1.

FTM Initiator k 1105 may receive Beamforming Report Poll (BSSID k,T4_(k−1)) frame 1190 at time T2_k 1150. After a SIFS interval followingthe end of reception of frame 1190, at time T3_k 1185, FTM Initiator k1105 may transmit CBF 1175 with CFI_k, time T2_k 1150, and time T3_k1175. CBF 1170 may be received by FTM Responder 1 at time T4_k 1180.

After a SIFS time interval following the end of reception of CBF 1175,FTM Responder 1 1115 may transmit frame 1195. Frame 1195 may take theform of an FTM ACK frame with time T4_k 1180 or a Beamforming ReportPoll (NULL, T4_k) frame with time T4_k 1180.

Round trip time for the k^(th) FTM Initiator (RTT_k) may be computed as(T4_k−T1_1)−(T3_k−T2_k) by both FTM Responder 1 1115 and FTM Initiator k1105.

FIG. 12 shows a multicast symmetric message flow 1200 with multipleinitiators with the ranging bit set. As shown in FIG. 12, NDPA frame maybe sent by FTM Responder 1 1215 at time T1 1225. FTM Responder 1 mayrecord the time of transmission of NDPA frame at time T1 1225. NDPAframe 1220 may be received by FTM Initiator 1 1210 at time T2 1230. TimeT2 1230 may be recorded by FTM Initiator 1210.

NDPA frame 1220 may be followed by transmission (by FTM Responder 11215) of frame 1240 at time T1_1 1235 after a time interval given bySIFS measured from the end of transmission of NDPA frame 1220. Frame1240 may take the form of an NDP_az frame with time T1_1 1235, an NDPframe, or a BRP frame. Frame 1240 may be received by FTM Initiator 11210 at time T2_1 1245. Time 2_1 1245 may be recorded by FTM Initiator 11210.

After a SIFS interval following the end of reception of frame 1240, attime T3_1 1255, FTM Initiator 1 1210 may transmit CBF 1260 with CFL1,time T2_1 1245, and time T3_1 1255. CBF 1260 may be received by FTMResponder 1 1215 at time T4_1 1265.

After a SIFS time interval, FTM Responder 1 1215 may transmitBeamforming Report Poll (BSSID of Initiator k, T4_(k−1)) frame 1290 withthe BSSID of FTM Initiator k 1205, where k≥2 is some integer and withtime T4_(k−1) 1265. For example, after a SIFS time interval, FTMResponder 1 1215 may transmit Beamforming Report Poll (BSSID k=2, T4_1)frame 1190 with the BSSID of FTM Initiator k=2 and T4_1.

FTM Initiator k 1205 may receive Beamforming Report Poll (BSSID ofInitiator k, T4_(k−1)) frame 1290 at time T2_k 1250. After a SIFSinterval following the end of reception of frame 1290, at time T3_k1285, FTM Initiator k 1205 may transmit CBF 1275 with CFI_k, time T2_k1250, and time 3_k 1275. CBF 1270 may be received by FTM Responder 1 attime T4_k 1280.

After a SIFS time interval following the end of reception of CBF 1275,FTM Responder 1 1215 may transmit frame 1295. Frame 1295 may take theform of an FTM ACK frame. In some embodiments, FTM ACK frame 1295 may besimilar in format to an FTM frame, but may be broadcast to FTMInitiators and heard by FTM Initiators.

At a time after T4_k, FTM Responder 1 1215 may transmit FTM ACK frame1295 with T1_1, T4_1 . . . T1_k, T4_k, AoA_1 . . . AoA_k, AoD_1 . . .AoD_k, Range_1 . . . Range_k, LCI_1 . . . LCI_k and Azimuth 1 . . .Azimuth_k. In some embodiments, FTM Ack frame 1295 may be a broadcastframe that contains AOD, AOA for each FTM Initiator. AoA_j refers to theAngle of Arrival of CBF frame from FTM Initiator j. AoD_j refers to theAngle of Departure of CBF frame from FTM Initiator j. Range_j, LCI_j andAzimuth_j, are the range, location context identifier and azimuth forFTM Initiator j, respectively, where 1≤j≤k. In some embodiments, FTM Ackframe 1295 may not transmitted be within a SIFS time interval ofreception of CBF with CFI_k and other information related to FTMInitiator k. In some embodiments, FTM Ack frame 1295 may include vectorentries which contain information relevant to the various FTMinitiators.

Round trip time for the k^(th) FTM Initiator (RTT_k) may be computed as(T4_k−T1_1)−(T3_k−T2_k) by both FTM Responder 1 1215 and FTM Initiator k1205.

FIG. 13 shows a multicast symmetric message flow 1300 with multipleinitiators with the ranging bit (e.g. in Reserved subfield 432 in FIG.4B) not set. As shown in FIG. 13, NDPA frame 1320 may be sent by FTMResponder 1 1315 at time T1 1325. FTM Responder 1 1315 may record thetime of transmission of NDPA frame at time T1 1325. NDPA frame 1320 maybe received by FTM Initiator 1 1310 at time T2 1330. Time T2 1330 may berecorded by FTM Initiator 1310.

NDPA frame 1320 may be followed by transmission (by FTM Responder 11315) of frame 1340 at time T1_1 1335 after a time interval given bySIFS measured from the end of transmission of NDPA frame 1320. Frame1340 may take the form of an NDP_az frame with time T1_1 1335, an NDPframe, or a BRP frame. Frame 1340 may be received by FTM Initiator 11310 at time T2_1 1345. Time 2_1 1345 may be recorded by FTM Initiator 11310.

After a SIFS interval following the end of reception of frame 1340, attime T3_1 1355, FTM Initiator 1 1310 may transmit CBF 1360 with CFL1,time T2_1 1345, and time T3_1 1355. CBF 1360 may be received by FTMResponder 1 1315 at time T4_1 1365.

After a SIFS time interval, at time T1_k 1370, FTM Responder 1 1315 maytransmit Beamforming Report Poll (BSSID of Initiator k, T4_(k−1))1390with the BSSID of FTM Initiator k 1305, where k≥2 is some integer andwith time T4_1 1365. FTM Initiator k 1305 may receive Beamforming ReportPoll (BSSID of Initiator k, T4_(k−1)) frame 1390 at time T2_k 1350.After a SIFS interval following the end of reception of frame 1390, attime T3_k 1385, FTM Initiator k 1305 may transmit CBF 1375 with CFI_k,time T2_k 1350, and time 3_k 1375. CBF 1370 may be received by FTMResponder 1 at time T4_k 1380.

In some embodiments, after time T4_K 1380, FTM Initiator 1 1310 maytransmit FTM Request for feedback information 1391 and FTM Responder 11315 may respond with FTM frame 1392 with information, including timeT1_1 1335, time T4_1 1365, AoA_1, AoD_1, Range_1, LCI_1, Azimuth_1, forFTM Initiator 1 1310. FTM Initiator 1 may respond with Ack frame 1393.

Similarly, any FTM Initiator k desiring feedback information maytransmit FTM Request for feedback information 1395 and FTM Responder 11315 may respond with FTM frame 1394 with information, including timeT1_k 1370, time T4_k 1380, AoA_k, AoD_k, Range_k, LCI_k, Azimuth_k, forFTM Initiator k 1305. FTM Initiator k may respond with Ack frame 1396.

The round trip time for the k^(th) FTM initiator, (RTT_k) may becomputed as (T4_k−T1_1)−(T3_k−T2_k) by both FTM Responder 1 1315 and FTMInitiator k 1305.

In FIG. 13, feedback is in the form of unicast FTM sessions for each FTMInitiator, which facilitates FTM initiator control over reception offeedback information. For example, FTM Initiators may control whetherthey receive feedback information.

FIG. 14A shows a multicast symmetric Orthogonal Frequency DivisionMultiple Access (OFDMA) message flow 1400 with multiple initiators whereinformation for all initiators is received within a SIFS interval. InFIG. 14A, the Responder does not share information. In FIG. 14A, OFDMAis used and synchronization between initiators and responders may befacilitated by exchanges of information and/or frames between initiatorsand responders. In contrast, some schemes, which respond to a multi-userNDP frame from an AP using time multiplexed responses by responders, mayfail to maintain adequate synchronization because of a lack oftransmissions by the AP.

As shown in FIG. 14A, NDPA frame 1420 (e.g. with broadcast bit inReserved subfield 432 set to 1) may be sent by Responder 1 1415. NDPAframe 1420 may be received by Initiator 1 1410 through Initiators k 1405

NDPA frame 1320 may be followed by transmission (by Responder 1 1415) ofNDP frame 1440 at time T1 1425 after a time interval given by SIFSmeasured from the end of transmission of NDPA frame 1420. NDP Frame 1440may be received by Initiators k at times given by T2_1, T2_2, . . .T2_k, respectively.

After a SIFS interval from the end of transmission of NDP frame 1440,Trigger frame 1460 may be transmitted by Responder 1 1415 at time Tlt1465 and received by Initiators k at times given by T2 t_1 1445, T2 t_2,. . . T2 t_k 1450, respectively.

After a SIFS interval from the end of reception of trigger frame 1460,CBF frames CBF(CFI1) 1490, CBF(CFI2), . . . CBF(CFI_k) 1475 may betransmitted at times t3_1 1455, t3_2, . . . t3_k 1485. The CBF framesare received by Responder 1 1415 at times T4_1 1480, T4_2, . . . T4_k1470. In some embodiments, the CBF frames may be multiplexed using OFDMAor uplink multi-user MIMO (UL MU-MIMO).

Round trip time for the k^(th) initiator RTT_k may be computed as:(T4_k−T1 t)−(T3_k−T2_k) by Responder 1 1415.

FIG. 14B shows a multicast symmetric Orthogonal Frequency DivisionMultiple Access (OFDMA) message flow 1487 with multiple initiators whereinformation for all initiators is received within a SIFS interval. FIG.14B shows some additional message exchanges relative to the message flowdepicted in FIG. 14A. Message flows and elements in common with FIG. 14Ahave been identified with the same reference numerals that were used inFIG. 14A.

In FIG. 14B, the Responder shares information (e.g. a bit in Reservedsubfield 432 in FIG. 4B may be set). In FIG. 14B, OFDMA is used andsynchronization between initiators and responders may be facilitated byexchanges of information and/or frames between initiators andresponders. In contrast, some schemes, which respond to a multi-user NDPframe from an AP using time multiplexed responses by responders, mayfail to maintain adequate synchronization because of a lack oftransmissions by the AP.

As shown in FIG. 14B, NDPA frame 1420 (e.g. with broadcast bit inReserved subfield 432 set to 1) may be sent by Responder 1 1415. NDPAframe 1420 may be received by Initiator 1 1410 through Initiators k 1405

NDPA frame 1320 may be followed by transmission (by Responder 1 1415) ofNDP frame 1440 at time T1 1425 after a time interval given by SIFSmeasured from the end of transmission of NDPA frame 1420. NDP Frame 1440may be received by Initiators k at times given by T2_1, T2_2, . . .T2_k, respectively.

After a SIFS interval from the end of transmission of NDP frame 1440,Trigger frame 1460 may be transmitted by Responder 1 1415 at time Tlt1465 and received by Initiators k at times given by T2 t_1 1445, T2 t_2,. . . T2 t_k 1450, respectively.

After a SIFS interval from the end of reception of trigger frame 1460,CBF frames CBF(CFI1) 1490, CBF(CFI2), . . . CBF(CFI_k) 1475 may betransmitted at times t3_1 1455, t3_2, . . . t3_k 1485. The CBF framesare received by Responder 1 1415 at times T4_1 1480, T4_2, . . . T4_k1470. In some embodiments, the CBF frames may be multiplexed using OFDMAor uplink multi-user MIMO (UL MU-MIMO).

Responder 1 1415 transmits FTM No Ack frame 1491 with time T1 t 1465,T4_1 1480, AoA, AoD, Azimuth to Initiator 1 1410 with FTM Ack bit set.Initiator 1415 responds with FTM Ack frame 1493 with time T2 t,_1 1445and time T3_1 1455.

Similarly, Responder 1 1415 may transmits FTM No Ack frame 1495 withtime Tlt 1465, T4_k 1470, AoA, AoD, Azimuth to Initiator k 1405 with FTMAck bit set. Initiator k 1405 responds with FTM Ack frame 1496 with timeT2 t,_k 1450 and time T3_k 1485. Round trip time for the k^(th)initiator RTT_k may be computed as: (T4_k−T1 t)−(T3_k−T2_k) by bothInitiators and Responders.

In some embodiments, the message flows shown in FIGS. 5A, 5B, 5E, 6, 7A,9A, 9B, and 9C, and 10-15 may be used based on capability informationreceived from a communicating device indicating support for one or moreprotocols in the figures.

FIG. 15 shows an example flowchart illustrating a method 1500 formessage flow between an initiator (e.g. a first STA) and responder (oneor more second STAs/UEs) in accordance with certain embodimentspresented herein.

In some embodiments, method 1500 may comprise, in block 1510transmitting, at a first time, a first NDPA frame to one or more secondstations (STAs), the first NDPA frame comprising a first bit indicatingthat one or more subsequent frames comprise ranging or angularinformation. In some embodiments, transmitting the first NDPA frame maycomprise unicasting the first NDPA frame to a corresponding STA in theone or more second STAs. In some embodiments, transmitting the firstNDPA frame may comprise broadcasting the first NDPA frame to the one ormore second STAs.

In block 1520, transmitting, after a Short Interval Frame Space (SIFS)time interval from the first time, a second frame, wherein the secondframe is one of: (a) a Null Data Packet az (NDP_az) frame withinformation about a time of transmission of the NDP_az frame, or (b) aNull Data Packet (NDP) frame, or (c) a Beam Refinement Protocol (BRP)frame.

In some embodiments, where the first NDPA frame is unicast, method 1500may further comprise: receiving, at the first STA, in response to thesecond frame, a Fine Timing Measurement (FTM) frame from thecorresponding STA. The FTM frame may include at least one of: a firsttiming information for Round Trip Time (RTT) calculations by the firstSTA, the first timing information comprising one or more of: a time ofarrival of the second frame at the corresponding STA, or a time oftransmission of the first FTM frame, or an Angle of Arrival (AoA) of thesecond frame; or an Angle of Departure (AoD) of the second frame; or aLocation Context Identifier (LCI) for the corresponding STA; or aChannel Feedback Information (CFI) field with information pertaining toa communication channel between the first STA and the corresponding STA,wherein the CFI field comprises one of: Channel Frequency Response (CFR)information, or Channel Impulse Response (CIR) information, or a subsetof the CIR information with arrival information of the second frame, orPower Delay Profile (PDP) information, or First Arrival Correction (FAC)information for the second frame. Further, in some embodiments, the FTMframe may comprise an acknowledgment response (or FTM Ack) bit, theacknowledgment response (FTM Ack) bit indicating that a response to thefirst FTM frame may be sent in the form of an FTM Acknowledgment (FTMAck) frame. The method may further comprise: transmitting, based, inpart, on the value of the acknowledgment response bit (or FTM Ack bit),an FTM Ack frame to the corresponding STA, the FTM Ack frame may includeone or more of: a second timing information, the second timinginformation comprising one or more of: a time of arrival of the FTMframe at the first STA, or a time of transmission of the FTM Ack frameby the first STA, or AoA information of the FTM frame; or AoDinformation of the FTM frame; or azimuth information pertaining to thecorresponding STA, or range information pertaining to the correspondingSTA.

In some embodiments, where the first NDPA frame is unicast, method 1500may further comprise: receiving, at the first STA, in response to thesecond frame, a Compressed Beamforming (CBF) frame, the CBF framecomprising one or more of: a Channel Feedback Information (CFI) fieldwith information pertaining to communication channel between the firstSTA and the corresponding STA, or timing information for Round Trip Time(RTT) calculations by the first STA, the timing information comprisingone or more of: a time of arrival of the second frame at thecorresponding STA, or a time of transmission of the CBF frame by thecorresponding STA.

In some embodiments, where the first NDPA frame is broadcast, method1500 may further comprise: receiving, at the first STA, in response tothe second frame, a first Compressed Beamforming (CBF) frame from afirst corresponding STA in the one or more second STAs, where the firstCBF frame may comprise: a first corresponding Channel FeedbackInformation (CFI) field with information pertaining to communicationchannel between the first STA and the first corresponding STA in the oneor more second STAs, a time of reception of the second frame at thefirst corresponding STA, and a time of transmission of the first CBFframe to the first STA. The method may further comprise: transmittingone or more Beamforming Report Poll (BRP) frames, wherein each BRP framecomprises a corresponding Basic Service Set Identifier (BSS ID)associated with a second corresponding STA of the one or more secondSTAs.

In some embodiments, the method may further comprise: receiving, inresponse to each of the one or more BRP frames, one or morecorresponding second CBF frames, wherein each corresponding second CBFframe is received from a second corresponding STA of the one or moresecond STAs, wherein each corresponding second CBF frame may comprise: asecond corresponding CFI field with information pertaining to acommunication channel between the first STA and the second correspondingSTA, a time of reception of a corresponding BRP frame at the secondcorresponding STA, and a time of transmission of the correspondingsecond CBF frame to the first STA.

In some embodiments, upon reception of a final corresponding second CBFframe received from a final second corresponding STA in response of theone or more BRP frames (e.g. the last received BRP frame), the methodmay further comprise transmitting an FTM Acknowledgment (FTM Ack) framewith the time of reception of the final corresponding second CBF frame;or an additional BRP frame with a null BSS ID and with the time ofreception of the final corresponding second CBF frame.

In some embodiments, upon reception of a final corresponding second CBFframe received from a final second corresponding STA in response of theone or more BRP frames (e.g. the last received BRP frame), the methodmay further comprise: broadcasting, an FTM Acknowledgment (FTM Ack)frame with one or more of: a time of transmission of the second frame,the time of reception of the first CBF frame and times of reception ofeach of the corresponding second CBF frames, or an Angle of Arrival(AoA) corresponding to the first CBF frame and Angles of Arrival of eachof the corresponding second CBF frames, or an Angle of Departure (AoD)corresponding to the first CBF frame and Angles of Departure of each ofthe corresponding second CBF frames, or a Range, or Location ContextIdentifier (LCI), or Azimuth for each of the one or more second STAs.

In some embodiments, the method may further comprise: receiving, from athird STA in the one or more second STAs, a Fine Timing Measurement(FTM) request for information. For example, the FTM request forinformation may be received after transmission/broadcast of the FTM Ackframe above (e.g. upon reception of the final corresponding second CBFframe). In response to the FTM request, the method my further comprisetransmitting an FTM frame to the third STA comprising one or more of: atime of transmission of a corresponding BRP frame to the third STA, thetime of reception of a corresponding second CBF frame from the thirdSTA, or an Angle of Arrival (AoA) of the corresponding second CBF framefrom the third STA, or an Angle of Departure (AoD) of the correspondingsecond CBF frame from the third STA, or a Range, or Location ContextIdentifier (LCI), or Azimuth for the third STA.

The method disclosed above may be performed by STA 100 (e.g. APs and/orUEs) and/or embodied on computer-readable media and executed by aprocessor on STA 100. Although the disclosure is illustrated inconnection with specific embodiments for instructional purposes,embodiments are not limited thereto. Various adaptations andmodifications may be made without departing from the scope. Therefore,the spirit and scope of the appended claims should not be limited to theforegoing description.

What is claimed is:
 1. A method on a first station (STA) comprising:transmitting, at a first time, a first Null Data Packet Announcement(NDPA) frame to one or more second stations (STAs), the first NDPA framecomprising at least one first bit indicating that an immediatelysubsequent second frame is to be used for ranging; and transmitting,after a Short Interval Frame Space (SIFS) time interval from the firsttime, the second frame, wherein the second frame is one of: a Null DataPacket az (NDP_az) frame with information about a time of transmissionof the NDP_az frame, or a Null Data Packet (NDP) frame, or a BeamRefinement Protocol (BRP) frame.
 2. The method of claim 1, wherein:transmitting the first NDPA frame comprises unicasting the first NDPAframe to a corresponding STA of the one or more second STAs; andtransmitting the second frame comprises unicasting the second frame tothe corresponding STA of the one or more second STAs.
 3. The method ofclaim 2, further comprising: receiving, at the first STA, in response tothe second frame, a Fine Timing Measurement (FTM) frame from thecorresponding STA with at least one of: a first timing information forRound Trip Time (RTT) calculations by the first STA, the first timinginformation comprising one or more of: a time of arrival of the secondframe at the corresponding STA, or a time of transmission of the FTMframe, or an Angle of Arrival (AoA) of the second frame; or an Angle ofDeparture (AoD) of the second frame; or a Location Context Identifier(LCI) for the corresponding STA; or a Channel Feedback Information (CFI)field with information pertaining to a communication channel between thefirst STA and the corresponding STA, wherein the CFI field comprises oneof: Channel Frequency Response (CFR) information, or Channel ImpulseResponse (CIR) information, or a subset of the CIR information witharrival information of the second frame, or Power Delay Profile (PDP)information, or First Arrival Correction (FAC) information for thesecond frame.
 4. The method of claim 3, wherein the FTM frame comprisesan acknowledgment response bit, the acknowledgment response bit toindicate whether a response to the FTM frame may be sent in the form ofan FTM Acknowledgment (FTM Ack) frame, and the method further comprises:transmitting, based, in part, on a value of the acknowledgment responsebit, an FTM Ack frame to the corresponding STA, the FTM Ack framecomprising one or more of: a second timing information, the secondtiming information comprising one or more of: a time of arrival of theFTM frame at the first STA, or a time of transmission of the FTM Ackframe by the first STA, or AoA information of the FTM frame; or AoDinformation of the FTM frame; or azimuth information pertaining to thecorresponding STA, or range information pertaining to the correspondingSTA.
 5. The method of claim 2, further comprising: receiving, at thefirst STA, in response to the second frame, a Compressed Beamforming(CBF) frame, the CBF frame comprising one or more of: a Channel FeedbackInformation (CFI) field with information pertaining to communicationchannel between the first STA and the corresponding STA, or timinginformation for Round Trip Time (RTT) calculations by the first STA, thetiming information comprising one or more of: a time of arrival of thesecond frame at the corresponding STA, or a time of transmission of theCBF frame by the corresponding STA.
 6. The method of claim 1, wherein:transmitting the first NDPA frame comprises broadcasting the first NDPAframe to the one or more second STAs; and transmitting the second framecomprises broadcasting the second frame to the one or more second STAs.7. The method of claim 6, further comprising: receiving, at the firstSTA, in response to the second frame, a first Compressed Beamforming(CBF) frame from a first corresponding STA in the one or more secondSTAs, the first CBF frame comprising: a first corresponding ChannelFeedback Information (CFI) field with information pertaining tocommunication channel between the first STA and the first correspondingSTA in the one or more second STAs, a time of reception of the secondframe at the first corresponding STA, and a time of transmission of thefirst CBF frame to the first STA.
 8. The method of claim 7, furthercomprising: transmitting one or more Beamforming Report Poll (BRP)frames, wherein each BRP frame comprises a corresponding Basic ServiceSet Identifier (BSS ID) associated with a second corresponding STA ofthe one or more second STAs.
 9. The method of claim 8, furthercomprising: receiving, in response to each of the one or more BRPframes, one or more corresponding second CBF frames, wherein eachcorresponding second CBF frame is received from a second correspondingSTA of the one or more second STAs, wherein each corresponding secondCBF frame comprises: a second corresponding CFI field with informationpertaining to a communication channel between the first STA and thesecond corresponding STA, a time of reception of a corresponding BRPframe at the second corresponding STA, and a time of transmission of thecorresponding second CBF frame to the first STA.
 10. The method of claim9, further comprising: transmitting, upon reception of a finalcorresponding second CBF frame received in response to the one or moreBRP frames from a final second corresponding STA of the one or moresecond STAs, one of: an FTM Acknowledgment (FTM Ack) frame with the timeof reception of the final corresponding second CBF frame; or anadditional BRP frame with a null BSS ID and with the time of receptionof the final corresponding second CBF frame.
 11. The method of claim 9,further comprising: broadcasting, upon reception of a finalcorresponding second CBF frame received in response to the one or moreBRP frames from a final second corresponding STA of the one or moresecond STAs, an FTM Acknowledgment (FTM Ack) frame with one or more of:a time of transmission of the second frame, the time of reception of thefirst CBF frame and times of reception of each of the correspondingsecond CBF frames, or an Angle of Arrival (AoA) corresponding to thefirst CBF frame and Angles of Arrival of each of the correspondingsecond CBF frames, or an Angle of Departure (AoD) corresponding to thefirst CBF frame and Angles of Departure of each of the correspondingsecond CBF frames, or a Range, or Location Context Identifier (LCI), orAzimuth for each of the one or more second STAs.
 12. The method of claim10, further comprising: receiving, from a third STA in the one or moresecond STAs, a Fine Timing Measurement (FTM) request for information;and transmitting, in response to the FTM request, an FTM frame to thethird STA comprising one or more of: a time of transmission of acorresponding BRP frame to the third STA, the time of reception of acorresponding second CBF frame from the third STA, or an Angle ofArrival (AoA) of the corresponding second CBF frame from the third STA,or an Angle of Departure (AoD) of the corresponding second CBF framefrom the third STA, or a Range, or Location Context Identifier (LCI), orAzimuth for the third STA.
 13. A first station (STA) comprising: amemory, and a processor coupled to the memory, wherein the processor isconfigured to: transmit, at a first time, a first Null Data PacketAnnouncement (NDPA) frame to one or more second stations (STAs), thefirst NDPA frame comprising at least one first bit indicating that animmediately subsequent second frame is to be used for ranging; andtransmit, after a Short Interval Frame Space (SIFS) time interval fromthe first time, the second frame, wherein the second frame is one of: aNull Data Packet az (NDP_az) frame with information about a time oftransmission of the NDP_az frame, or a Null Data Packet (NDP) frame, ora Beam Refinement Protocol (BRP) frame.
 14. The first STA of claim 13,wherein the processor is configured to: transmit the first NDPA frame byunicasting the first NDPA frame to a corresponding STA of the one ormore second STAs; and transmit the second frame by unicasting the secondframe to the corresponding STA of the one or more second STAs.
 15. Thefirst STA of claim 14, wherein the processor is further configured to:receive, at the first STA, in response to the second frame, a FineTiming Measurement (FTM) frame from the corresponding STA with at leastone of: a first timing information for Round Trip Time (RTT)calculations by the first STA, the first timing information comprisingone or more of: a time of arrival of the second frame at thecorresponding STA, or a time of transmission of the FTM frame, or anAngle of Arrival (AoA) of the second frame; or an Angle of Departure(AoD) of the second frame; or a Location Context Identifier (LCI) forthe corresponding STA; or a Channel Feedback Information (CFI) fieldwith information pertaining to a communication channel between the firstSTA and the corresponding STA, wherein the CFI field comprises one of:Channel Frequency Response (CFR) information, or Channel ImpulseResponse (CIR) information, or a subset of the CIR information witharrival information of the second frame, or Power Delay Profile (PDP)information, or First Arrival Correction (FAC) information for thesecond frame.
 16. The first STA of claim 15, wherein the FTM framecomprises an acknowledgment response bit, the acknowledgment responsebit indicating whether a response to the FTM frame may be sent in theform of an FTM Acknowledgment (FTM Ack) frame, and the processor isfurther configured to: transmit, based, in part, on a value of theacknowledgment response bit, an FTM Ack frame to the corresponding STA,the FTM Ack frame comprising one or more of: a second timinginformation, the second timing information comprising one or more of: atime of arrival of the FTM frame at the first STA, or a time oftransmission of the FTM Ack frame by the first STA, or AoA informationof the FTM frame; or AoD information of the FTM frame; or azimuthinformation pertaining to the corresponding STA, or range informationpertaining to the corresponding STA.
 17. The first STA of claim 14,wherein the processor is further configured to: receive, at the firstSTA, in response to the second frame, a Compressed Beamforming (CBF)frame, the CBF frame comprising one or more of: a Channel FeedbackInformation (CFI) field with information pertaining to communicationchannel between the first STA and the corresponding STA, or timinginformation for Round Trip Time (RTT) calculations by the first STA, thetiming information comprising one or more of: a time of arrival of thesecond frame at the corresponding STA, or a time of transmission of theCBF frame by the corresponding STA.
 18. The first STA of claim 13,wherein the processor is configured to: transmit the first NDPA frame bybroadcasting the first NDPA frame to the one or more second STAs; andtransmit the second frame by broadcasting the first NDPA frame to acorresponding STA of the one or more second STAs.
 19. The first STA ofclaim 18, wherein the processor is further configured to: receive, atthe first STA, in response to the second frame, a first CompressedBeamforming (CBF) frame from a first corresponding STA in the one ormore second STAs, the first CBF frame comprising: a first correspondingChannel Feedback Information (CFI) field with information pertaining tocommunication channel between the first STA and the first correspondingSTA in the one or more second STAs, a time of reception of the secondframe at the first corresponding STA, and a time of transmission of thefirst CBF frame to the first STA.
 20. The first STA of claim 19, whereinthe processor is further configured to: transmit one or more BeamformingReport Poll (BRP) frames, wherein each BRP frame comprises acorresponding Basic Service Set Identifier (BSS ID) associated with asecond corresponding STA of the one or more second STAs.
 21. The firstSTA of claim 20, wherein the processor is further configured to:receive, in response to each of the one or more BRP frames, acorresponding second CBF frame, wherein each corresponding second CBFframe is received from the second corresponding STA of the one or moresecond STAs, wherein each corresponding second CBF frame comprises: asecond corresponding CFI field pertaining to communication channelbetween the first STA and the second corresponding STA, a time ofreception of a corresponding BRP frame at the second corresponding STA,and a time of transmission of the corresponding second CBF frame to thefirst STA.
 22. The first STA of claim 21, wherein the processor isfurther configured to: transmit, upon reception of a final correspondingsecond CBF frame received in response to the one or more BRP frames froma final second corresponding STA of the one or more second STAs, one of:an FTM Acknowledgment (FTM Ack) frame with the time of reception of thefinal corresponding second CBF frame; or an additional BRP frame with anull BSS ID and with the time of reception of the final correspondingsecond CBF frame.
 23. The first STA of claim 21, wherein the processoris further configured to: broadcast, upon reception of a finalcorresponding second CBF frame received in response the one or more BRPframes from a final second corresponding STA of the one or more secondSTAs, an FTM Acknowledgment (FTM Ack) frame with one or more of: a timeof transmission of the second frame, the time of reception of the firstCBF frame and times of reception of each of the corresponding second CBFframes, or an Angle of Arrival (AoA) corresponding to the first CBFframe and Angles of Arrival of each of the corresponding second CBFframes, or an Angle of Departure (AoD) corresponding to the first CBFframe and Angles of Departure of each of the corresponding second CBFframes, or a Range, or Location Context Identifier (LCI), or Azimuth foreach of the one or more second STAs.
 24. The first STA of claim 22,wherein the processor is further configured to: receive, from a thirdSTA in the one or more second STAs, a Fine Timing Measurement (FTM)request for information; and transmit, in response to the FTM request,an FTM frame to the third STA comprising one or more of: a time oftransmission of a corresponding BRP frame to the third STA, the time ofreception of a corresponding second CBF frame from the third STA, or anAngle of Arrival (AoA) of the corresponding second CBF frame from thethird STA, or an Angle of Departure (AoD) of the corresponding secondCBF frame from the third STA, or a Range, or Location Context Identifier(LCI), or Azimuth for the third STA.
 25. A first station (STA)comprising: means for transmitting a first Null Data Packet Announcement(NDPA) frame to one or more second stations (STAs), the first NDPA framecomprising at least one first bit indicating that an immediatelysubsequent second frame is to be used for ranging; and means fortransmitting, after a Short Interval Frame Space (SIFS) time interval,the second frame, wherein the second frame is one of: a Null Data Packetaz (NDP_az) frame with information about a time of transmission of theNDP_az frame, or a Null Data Packet (NDP) frame, or a Beam RefinementProtocol (BRP) frame.
 26. The first STA of claim 25, wherein: means fortransmitting the first NDPA frame comprises means for unicasting thefirst NDPA frame to a corresponding STA of the one or more second STAs,and means for transmitting the second frame comprises means forunicasting the second frame to the corresponding STA of the one or moresecond STAs; and the first STA further comprises: means for receiving,at the first STA, in response to the second frame, a Fine TimingMeasurement (FTM) frame from the corresponding STA with at least one of:a first timing information for Round Trip Time (RTT) calculations by thefirst STA, the first timing information comprising one or more of: atime of arrival of the second frame at the corresponding STA, or a timeof transmission of the FTM frame, or an Angle of Arrival (AoA) of thesecond frame; or an Angle of Departure (AoD) of the second frame; or aLocation Context Identifier (LCI) for the corresponding STA; or aChannel Feedback Information (CFI) field with information pertaining toa communication channel between the first STA and the corresponding STA,wherein the CFI field comprises one of: Channel Frequency Response (CFR)information, or Channel Impulse Response (CIR) information, or a subsetof the CIR information with arrival information of the second frame, orPower Delay Profile (PDP) information, or First Arrival Correction (FAC)information for the second frame.
 27. The first STA of claim 25, whereinmeans for transmitting the first NDPA frame comprises means forbroadcasting the first NDPA frame to the one or more second STAs, andmeans for transmitting the second frame comprises means for broadcastingthe second frame to the one or more second STAs, and the first STAfurther comprises: means for receiving, at the first STA, in response tothe second frame, a first Compressed Beamforming (CBF) frame from afirst corresponding STA in the one or more second STAs, the first CBFframe comprising: a first corresponding Channel Feedback Information(CFI) field pertaining to communication channel between the first STAand the first corresponding STA in the one or more second STAs, a timeof reception of the second frame at the first corresponding STA, and atime of transmission of the first CBF frame to the first STA.
 28. Anon-transitory computer-readable medium comprising code executable by aprocessor to: transmit a first Null Data Packet Announcement (NDPA)frame to one or more second stations (STAs), the first NDPA framecomprising at least one first bit indicating that an immediatelysubsequent second frame is to be used for ranging; and transmit, after aShort Interval Frame Space (SIFS) time interval, a second frame, whereinthe second frame is one of: a Null Data Packet az (NDP_az) frame withinformation about a time of transmission of the NDP_az frame, or a NullData Packet (NDP) frame, or a Beam Refinement Protocol (BRP) frame. 29.The computer-readable medium of claim 28, wherein the code executable bythe processor to: transmit the first NDPA frame unicasts the first NDPAframe to a corresponding STA of the one or more second STAs, andtransmit the second frame unicasts the second frame to the correspondingSTA of the one or more second STAs; and the medium further comprisescode executable by the processor to: receive, at the first STA, inresponse to the second frame, a Fine Timing Measurement (FTM) frame fromthe corresponding STA with at least one of: a first timing informationfor Round Trip Time (RTT) calculations by the first STA, the firsttiming information comprising one or more of: a time of arrival of thesecond frame at the corresponding STA, or a time of transmission of theFTM frame, or an Angle of Arrival (AoA) of the second frame; or an Angleof Departure (AoD) of the second frame; or a Location Context Identifier(LCI) for the corresponding STA; or a Channel Feedback Information (CFI)field with information pertaining to a communication channel between thefirst STA and the corresponding STA, wherein the CFI field comprises oneof: Channel Frequency Response (CFR) information, or Channel ImpulseResponse (CIR) information, or a subset of the CIR information witharrival information of the second frame, or Power Delay Profile (PDP)information, or First Arrival Correction (FAC) information for thesecond frame.
 30. The computer-readable medium of claim 28, wherein thecode executable by the processor to: transmit the first NDPA framebroadcasts the first NDPA frame to the one or more second STAs, andtransmit the second frame broadcasts the second frame to the one or moresecond STAs; and the medium further comprises code executable by theprocessor to: receive, at the first STA, in response to the secondframe, a first Compressed Beamforming (CBF) frame from a firstcorresponding STA in the one or more second STAs, the first CBF framecomprising one or more of: a first corresponding Channel FeedbackInformation (CFI) field with information pertaining to communicationchannel between the first STA and the first corresponding STA in the oneor more second STAs, a time of reception of the second frame at thefirst corresponding STA, and a time of transmission of the first CBFframe to the first STA.